[lkml]   [2018]   [Nov]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
From automated boot bisection reports
tl;dr automatic bisection reports are enabled for mainline and stable

In case you're not already familiar with it, the project
is a community effort to build and test upstream kernel trees on a
variety of hardware platforms. Reports are mostly sent to the
kernel-build-reports mailing list[1] and all the results can be seen

When a boot test regression is detected on mainline or stable
branches, a bisection is automatically run. Starting from today, an
email report will be automatically sent to a list of recipients based
on the commit the bisection has found (author, trailers, maintainers
and lists associated with the code changed by the commit). Until
now, the results were manually curated and only reported more widely
when they seemed valid. Some automated checks are now used, they
have been showing good results for a while with no false positives.

There shouldn't be many bisection reports yet, typically one or two
every month. As we'll start bisecting other trees such as linux-next
and other test results than just plain boots, the volume may start
increasing gradually over the coming months.

Please let us know if you would like the report format to be changed
when you get one, or if you have any suggestions at all.

Hope this helps!



 \ /
  Last update: 2018-11-23 11:23    [W:0.022 / U:0.236 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site