On Thu 2019-06-06 08:49:43, Philip Li wrote: > On Wed, Jun 05, 2019 at 10:51:53AM -0400, Joe Lawrence wrote: > > On 6/5/19 10:31 AM, Philip Li wrote: > > >On Wed, Jun 05, 2019 at 09:48:02AM -0400, Joe Lawrence wrote: > > That's okay, though I guess I'm not clear why there wasn't an email > > reporting that the livepatching selftests failed after > > livepatching.git was recently updated to include tglx's stack trace > > fixes. > > > > Do the tests only run for unique commits (ie, will it skip when > > livepatching.git updates/merges latest linux tree ??) > it will not skip, though we are not testing commit by commit. If the issue > is found, and bisect to the bad commit, we will report to author of that > commit for information. Bisecting might take a lot of time or even fail. But each selftest should get associated with a kernel subsystem. It would be helpful to always inform the subsystem maintainers. Or at least the author of the selftest that failed. Best Regards, Petr
