On June 10, 2018 12:46:46 AM PDT, Andy Shevchenko <andy.shevchenko@xxxxxxxxx> wrote: >On Sat, Jun 9, 2018 at 6:19 AM, kbuild test robot <lkp@xxxxxxxxx> >wrote: >> tree: >git://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git >for-next >> head: 2da502a0aea723e811a71d78129ed5a9f730129b >> commit: 2da502a0aea723e811a71d78129ed5a9f730129b [6/6] platform/x86: >silead_dmi: Add touchscreen info for the Chuwi Vi10 tablet >> config: x86_64-randconfig-s1-06091036 (attached as .config) >> compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026 >> reproduce: >> git checkout 2da502a0aea723e811a71d78129ed5a9f730129b >> # save the attached .config to linux build tree >> make ARCH=x86_64 >> > >Hmm... IIRC I got success builds from the 0-day bot. Hans, does it >mean we have bisectability issue? > >Darren, should I rebase for-next to fix this? I would, yes. Rebasing is bad. Pushing known bugs to mainline is worse. We need to step up our own CI. 0 day is a great safety net, but stuff like this we should be catching ourselves. I'll check if my Jenkins build caught it, and we need to enable email notification. I've also considered moving to Travis CI. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
