Re: rmk/for-next boot: 110 boots: 8 failed, 98 passed with 4 untried/unknown (v4.16-rc2-29-g6dc8c9d147dd)

On Fri, Apr 20, 2018 at 08:59:02AM -0700, kernelci.org bot wrote:

at91_dt_defconfig:
    at91sam9m10g45ek:
        lab-free-electrons: new failure (last pass: v4.16-rc2-29-gf592819553ca)
    at91sam9x35ek:
        lab-free-electrons: new failure (last pass: v4.16-rc2-29-gf592819553ca)

multi_v7_defconfig:
    sun5i-gr8-chip-pro:
        lab-free-electrons: failing since 3 days (last pass: v4.16-rc2-28-g7cafa5c7a73e - first fail: v4.16-rc2-29-gf592819553ca)

multi_v7_defconfig+CONFIG_SMP=n:
    at91-sama5d4_xplained:
        lab-free-electrons: new failure (last pass: v4.16-rc2-29-gf592819553ca)
    omap3-beagle-xm:
        lab-free-electrons: failing since 14 days (last pass: v4.14-rc1-47-g4dd490dc84fd - first fail: v4.16-rc2-24-gf85aba3f0953)

sama5_defconfig:
    at91-sama5d4_xplained:
        lab-free-electrons: new failure (last pass: v4.16-rc2-29-gf592819553ca)

sunxi_defconfig:
    sun5i-gr8-chip-pro:
        lab-free-electrons: new failure (last pass: v4.16-rc2-29-gf592819553ca)
    sun8i-a83t-allwinner-h8homlet-v2:
        lab-free-electrons: new failure (last pass: v4.16-rc2-29-gf592819553ca)

The above are slightly worrying - nothing should have affected those that last passed with v4.16-rc2-29-gf592819553ca. The only change is to change the sed expression to get the kernel BSS size to be a little more lenient with certain toolchains - but if it wasn't working previously the build should have failed.

Any chance of some investigation of this regression before I push the commits upstream to Linus?