lkml.org 
[lkml]   [2016]   [Apr]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC][PATCH 00/31] implement atomic_fetch_$op
    On Fri, Apr 22, 2016 at 11:44:55AM +0200, Peter Zijlstra wrote:
    > On Fri, Apr 22, 2016 at 11:04:13AM +0200, Peter Zijlstra wrote:
    > > The one that I did not do was ARMv8.1-LSE and I was hoping Will would help out
    > > with that. Also, it looks like the 0-day built bot does not do arm64 builds,
    > > people might want to look into that.
    >
    > OK, weirdness. I received the "BUILD SUCCESS" email without any arm64
    > builds listed, but I just received a build bot email telling me the
    > arm64 build was borked (which I know it is).

    Sorry, that may happen because even though most errors will be
    detected in the first hour or before the BUILD SUCCESS/DONE
    notification, the build/boot/performance tests for a particular branch
    may continue for days, during the time test coverage keeps growing.
    Which means it's possible to receive a build failure after receiving
    BUILD SUCCESS notification.

    In particular, 0-day bot classify 500+ kconfigs into 2 priority lists:

    P1: 100+ realtime priority kconfigs which should be finished before sending
    out BUILD SUCCESS notification

    P2: 400+ background priority kconfigs which may take hours to days to finish

    That split is a tradeoff between timeliness and completeness. It turns
    out to work well as long as we choose the suitable P1 list.

    So the more accurate interpretation of "BUILD SUCCESS/DONE" would be:
    0day bot is working on your tree (no worry about out-of-service) and
    reached a major milestone.

    I'll add arm64-defconfig to P1 list to improve its coverage.

    Thanks,
    Fengguang

    \
     
     \ /
      Last update: 2016-04-22 15:21    [W:4.050 / U:0.012 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site