next-clang/master build: 4 builds: 1 failed, 3 passed, 94 warnings (next-20190508)
Full Build Summary: https://staging.kernelci.org/build/next-clang/branch/master/kernel/next-2019...
Tree: next-clang Branch: master Git Describe: next-20190508 Git Commit: 31ccad9ba50305d346c6a07760e7ef37686219b9 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Built: 1 unique architecture
Build Failure Detected:
arm64: allmodconfig: (clang-8) FAIL
Warnings Detected:
arm64: allnoconfig (clang-8): 13 warnings defconfig (clang-8): 68 warnings tinyconfig (clang-8): 13 warnings
Warnings summary:
4 <stdin>:1403:2: warning: syscall fspick not implemented [-W#warnings] 4 <stdin>:1400:2: warning: syscall fsmount not implemented [-W#warnings] 4 <stdin>:1397:2: warning: syscall fsconfig not implemented [-W#warnings] 4 <stdin>:1394:2: warning: syscall fsopen not implemented [-W#warnings] 4 <stdin>:1391:2: warning: syscall move_mount not implemented [-W#warnings] 4 <stdin>:1388:2: warning: syscall open_tree not implemented [-W#warnings] 4 6 warnings generated. 4 #warning syscall open_tree not implemented 4 #warning syscall move_mount not implemented 4 #warning syscall fspick not implemented 4 #warning syscall fsopen not implemented 4 #warning syscall fsmount not implemented 4 #warning syscall fsconfig not implemented 3 drivers/soc/rockchip/pm_domains.c:832:20: warning: shift count is negative [-Wshift-count-negative] 3 drivers/soc/rockchip/pm_domains.c:820:21: warning: shift count is negative [-Wshift-count-negative] 3 drivers/soc/rockchip/pm_domains.c:819:22: warning: shift count is negative [-Wshift-count-negative] 3 drivers/soc/rockchip/pm_domains.c:818:22: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:834:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:833:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:822:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:821:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:796:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:795:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:794:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:793:22: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:792:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:791:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:790:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:789:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:788:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:752:21: warning: shift count is negative [-Wshift-count-negative] 1 drivers/soc/rockchip/pm_domains.c:747:21: warning: shift count is negative [-Wshift-count-negative] 1 41 warnings generated.
================================================================================
Detailed per-defconfig build reports:
-------------------------------------------------------------------------------- allnoconfig (arm64, clang-8) — PASS, 0 errors, 13 warnings, 0 section mismatches
Warnings: <stdin>:1388:2: warning: syscall open_tree not implemented [-W#warnings] #warning syscall open_tree not implemented <stdin>:1391:2: warning: syscall move_mount not implemented [-W#warnings] #warning syscall move_mount not implemented <stdin>:1394:2: warning: syscall fsopen not implemented [-W#warnings] #warning syscall fsopen not implemented <stdin>:1397:2: warning: syscall fsconfig not implemented [-W#warnings] #warning syscall fsconfig not implemented <stdin>:1400:2: warning: syscall fsmount not implemented [-W#warnings] #warning syscall fsmount not implemented <stdin>:1403:2: warning: syscall fspick not implemented [-W#warnings] #warning syscall fspick not implemented 6 warnings generated.
-------------------------------------------------------------------------------- defconfig (arm64, clang-8) — PASS, 0 errors, 68 warnings, 0 section mismatches
Warnings: <stdin>:1388:2: warning: syscall open_tree not implemented [-W#warnings] #warning syscall open_tree not implemented <stdin>:1391:2: warning: syscall move_mount not implemented [-W#warnings] #warning syscall move_mount not implemented <stdin>:1394:2: warning: syscall fsopen not implemented [-W#warnings] #warning syscall fsopen not implemented <stdin>:1397:2: warning: syscall fsconfig not implemented [-W#warnings] #warning syscall fsconfig not implemented <stdin>:1400:2: warning: syscall fsmount not implemented [-W#warnings] #warning syscall fsmount not implemented <stdin>:1403:2: warning: syscall fspick not implemented [-W#warnings] #warning syscall fspick not implemented 6 warnings generated. drivers/soc/rockchip/pm_domains.c:747:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:752:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:752:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:788:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:788:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:789:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:789:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:790:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:790:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:791:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:791:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:792:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:792:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:793:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:793:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:794:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:794:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:795:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:795:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:796:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:796:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:818:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:818:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:818:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:819:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:819:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:819:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:820:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:820:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:820:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:821:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:821:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:822:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:822:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:832:20: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:832:20: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:832:20: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:833:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:833:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:834:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:834:21: warning: shift count is negative [-Wshift-count-negative] 41 warnings generated. <stdin>:1388:2: warning: syscall open_tree not implemented [-W#warnings] #warning syscall open_tree not implemented <stdin>:1391:2: warning: syscall move_mount not implemented [-W#warnings] #warning syscall move_mount not implemented <stdin>:1394:2: warning: syscall fsopen not implemented [-W#warnings] #warning syscall fsopen not implemented <stdin>:1397:2: warning: syscall fsconfig not implemented [-W#warnings] #warning syscall fsconfig not implemented <stdin>:1400:2: warning: syscall fsmount not implemented [-W#warnings] #warning syscall fsmount not implemented <stdin>:1403:2: warning: syscall fspick not implemented [-W#warnings] #warning syscall fspick not implemented 6 warnings generated.
-------------------------------------------------------------------------------- tinyconfig (arm64, clang-8) — PASS, 0 errors, 13 warnings, 0 section mismatches
Warnings: <stdin>:1388:2: warning: syscall open_tree not implemented [-W#warnings] #warning syscall open_tree not implemented <stdin>:1391:2: warning: syscall move_mount not implemented [-W#warnings] #warning syscall move_mount not implemented <stdin>:1394:2: warning: syscall fsopen not implemented [-W#warnings] #warning syscall fsopen not implemented <stdin>:1397:2: warning: syscall fsconfig not implemented [-W#warnings] #warning syscall fsconfig not implemented <stdin>:1400:2: warning: syscall fsmount not implemented [-W#warnings] #warning syscall fsmount not implemented <stdin>:1403:2: warning: syscall fspick not implemented [-W#warnings] #warning syscall fspick not implemented 6 warnings generated.
--- For more info write to info@kernelci.org
From: kernelci.org bot bot@kernelci.org Date: Wed, May 8, 2019 at 3:38 AM To: natechancellor@gmail.com, broonie@kernel.org, arnd.bergmann@linaro.org, ndesaulniers@google.com, kernel-build-reports@lists.linaro.org, trong@google.com, matthew.hart@linaro.org
next-clang/master build: 4 builds: 1 failed, 3 passed, 94 warnings (next-20190508)
Full Build Summary: https://staging.kernelci.org/build/next-clang/branch/master/kernel/next-2019...
Tree: next-clang Branch: master Git Describe: next-20190508 Git Commit: 31ccad9ba50305d346c6a07760e7ef37686219b9 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Built: 1 unique architecture
Build Failure Detected:
arm64: allmodconfig: (clang-8) FAIL
Any idea what FAIL means? The below 3 builds have their warnings listed, but allmodconfig just says FAIL. Maybe the build timed out?
Warnings Detected:
arm64: allnoconfig (clang-8): 13 warnings defconfig (clang-8): 68 warnings tinyconfig (clang-8): 13 warnings
Warnings summary:
4 <stdin>:1403:2: warning: syscall fspick not implemented [-W#warnings] 4 <stdin>:1400:2: warning: syscall fsmount not implemented [-W#warnings] 4 <stdin>:1397:2: warning: syscall fsconfig not implemented [-W#warnings] 4 <stdin>:1394:2: warning: syscall fsopen not implemented [-W#warnings] 4 <stdin>:1391:2: warning: syscall move_mount not implemented [-W#warnings] 4 <stdin>:1388:2: warning: syscall open_tree not implemented [-W#warnings] 4 6 warnings generated. 4 #warning syscall open_tree not implemented 4 #warning syscall move_mount not implemented 4 #warning syscall fspick not implemented 4 #warning syscall fsopen not implemented 4 #warning syscall fsmount not implemented 4 #warning syscall fsconfig not implemented 3 drivers/soc/rockchip/pm_domains.c:832:20: warning: shift count is negative [-Wshift-count-negative] 3 drivers/soc/rockchip/pm_domains.c:820:21: warning: shift count is negative [-Wshift-count-negative] 3 drivers/soc/rockchip/pm_domains.c:819:22: warning: shift count is negative [-Wshift-count-negative] 3 drivers/soc/rockchip/pm_domains.c:818:22: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:834:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:833:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:822:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:821:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:796:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:795:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:794:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:793:22: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:792:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:791:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:790:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:789:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:788:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:752:21: warning: shift count is negative [-Wshift-count-negative] 1 drivers/soc/rockchip/pm_domains.c:747:21: warning: shift count is negative [-Wshift-count-negative] 1 41 warnings generated.================================================================================
Detailed per-defconfig build reports:
allnoconfig (arm64, clang-8) — PASS, 0 errors, 13 warnings, 0 section mismatches
Warnings: <stdin>:1388:2: warning: syscall open_tree not implemented [-W#warnings] #warning syscall open_tree not implemented <stdin>:1391:2: warning: syscall move_mount not implemented [-W#warnings] #warning syscall move_mount not implemented <stdin>:1394:2: warning: syscall fsopen not implemented [-W#warnings] #warning syscall fsopen not implemented <stdin>:1397:2: warning: syscall fsconfig not implemented [-W#warnings] #warning syscall fsconfig not implemented <stdin>:1400:2: warning: syscall fsmount not implemented [-W#warnings] #warning syscall fsmount not implemented <stdin>:1403:2: warning: syscall fspick not implemented [-W#warnings] #warning syscall fspick not implemented 6 warnings generated.
defconfig (arm64, clang-8) — PASS, 0 errors, 68 warnings, 0 section mismatches
Warnings: <stdin>:1388:2: warning: syscall open_tree not implemented [-W#warnings] #warning syscall open_tree not implemented <stdin>:1391:2: warning: syscall move_mount not implemented [-W#warnings] #warning syscall move_mount not implemented <stdin>:1394:2: warning: syscall fsopen not implemented [-W#warnings] #warning syscall fsopen not implemented <stdin>:1397:2: warning: syscall fsconfig not implemented [-W#warnings] #warning syscall fsconfig not implemented <stdin>:1400:2: warning: syscall fsmount not implemented [-W#warnings] #warning syscall fsmount not implemented <stdin>:1403:2: warning: syscall fspick not implemented [-W#warnings] #warning syscall fspick not implemented 6 warnings generated. drivers/soc/rockchip/pm_domains.c:747:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:752:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:752:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:788:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:788:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:789:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:789:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:790:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:790:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:791:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:791:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:792:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:792:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:793:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:793:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:794:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:794:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:795:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:795:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:796:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:796:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:818:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:818:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:818:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:819:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:819:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:819:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:820:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:820:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:820:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:821:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:821:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:822:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:822:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:832:20: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:832:20: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:832:20: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:833:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:833:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:834:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:834:21: warning: shift count is negative [-Wshift-count-negative] 41 warnings generated. <stdin>:1388:2: warning: syscall open_tree not implemented [-W#warnings] #warning syscall open_tree not implemented <stdin>:1391:2: warning: syscall move_mount not implemented [-W#warnings] #warning syscall move_mount not implemented <stdin>:1394:2: warning: syscall fsopen not implemented [-W#warnings] #warning syscall fsopen not implemented <stdin>:1397:2: warning: syscall fsconfig not implemented [-W#warnings] #warning syscall fsconfig not implemented <stdin>:1400:2: warning: syscall fsmount not implemented [-W#warnings] #warning syscall fsmount not implemented <stdin>:1403:2: warning: syscall fspick not implemented [-W#warnings] #warning syscall fspick not implemented 6 warnings generated.
tinyconfig (arm64, clang-8) — PASS, 0 errors, 13 warnings, 0 section mismatches
Warnings: <stdin>:1388:2: warning: syscall open_tree not implemented [-W#warnings] #warning syscall open_tree not implemented <stdin>:1391:2: warning: syscall move_mount not implemented [-W#warnings] #warning syscall move_mount not implemented <stdin>:1394:2: warning: syscall fsopen not implemented [-W#warnings] #warning syscall fsopen not implemented <stdin>:1397:2: warning: syscall fsconfig not implemented [-W#warnings] #warning syscall fsconfig not implemented <stdin>:1400:2: warning: syscall fsmount not implemented [-W#warnings] #warning syscall fsmount not implemented <stdin>:1403:2: warning: syscall fspick not implemented [-W#warnings] #warning syscall fspick not implemented 6 warnings generated.
For more info write to info@kernelci.org
On Thu, 9 May 2019 at 18:41, Nick Desaulniers ndesaulniers@google.com wrote:
From: kernelci.org bot bot@kernelci.org Date: Wed, May 8, 2019 at 3:38 AM To: natechancellor@gmail.com, broonie@kernel.org, arnd.bergmann@linaro.org, ndesaulniers@google.com, kernel-build-reports@lists.linaro.org, trong@google.com, matthew.hart@linaro.org
next-clang/master build: 4 builds: 1 failed, 3 passed, 94 warnings (next-20190508)
Full Build Summary: https://staging.kernelci.org/build/next-clang/branch/master/kernel/next-2019...
Tree: next-clang Branch: master Git Describe: next-20190508 Git Commit: 31ccad9ba50305d346c6a07760e7ef37686219b9 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Built: 1 unique architecture
Build Failure Detected:
arm64: allmodconfig: (clang-8) FAIL
Any idea what FAIL means? The below 3 builds have their warnings listed, but allmodconfig just says FAIL. Maybe the build timed out?
Hey Nick, doesnt look like the build timed out as it showing in the UI: https://staging.kernelci.org/build/id/5cd2aba2cf3a0f83c38dcaec/
I think whats happened here is the email has not been rendered properly. I'm currently working on a patch that fixes many issues with the build emails (it's why clang builds haven't moved to the production setup yet) and my work-in-progress branch has been merged onto staging recently so there could be some transient errors with emails.
The good news is that the build log is available: http://staging-storage.kernelci.org/next-clang/master/next-20190508/arm64/al...
Also, KernelCI can produce a plaintext email (like this one), or a HTML email with clickable links to the build logs, should I switch to the HTML emails so it's easier in future for you to find the log files?
Warnings Detected:
arm64: allnoconfig (clang-8): 13 warnings defconfig (clang-8): 68 warnings tinyconfig (clang-8): 13 warnings
Warnings summary:
4 <stdin>:1403:2: warning: syscall fspick not implemented [-W#warnings] 4 <stdin>:1400:2: warning: syscall fsmount not implemented [-W#warnings] 4 <stdin>:1397:2: warning: syscall fsconfig not implemented [-W#warnings] 4 <stdin>:1394:2: warning: syscall fsopen not implemented [-W#warnings] 4 <stdin>:1391:2: warning: syscall move_mount not implemented [-W#warnings] 4 <stdin>:1388:2: warning: syscall open_tree not implemented [-W#warnings] 4 6 warnings generated. 4 #warning syscall open_tree not implemented 4 #warning syscall move_mount not implemented 4 #warning syscall fspick not implemented 4 #warning syscall fsopen not implemented 4 #warning syscall fsmount not implemented 4 #warning syscall fsconfig not implemented 3 drivers/soc/rockchip/pm_domains.c:832:20: warning: shift count is negative [-Wshift-count-negative] 3 drivers/soc/rockchip/pm_domains.c:820:21: warning: shift count is negative [-Wshift-count-negative] 3 drivers/soc/rockchip/pm_domains.c:819:22: warning: shift count is negative [-Wshift-count-negative] 3 drivers/soc/rockchip/pm_domains.c:818:22: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:834:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:833:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:822:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:821:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:796:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:795:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:794:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:793:22: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:792:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:791:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:790:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:789:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:788:21: warning: shift count is negative [-Wshift-count-negative] 2 drivers/soc/rockchip/pm_domains.c:752:21: warning: shift count is negative [-Wshift-count-negative] 1 drivers/soc/rockchip/pm_domains.c:747:21: warning: shift count is negative [-Wshift-count-negative] 1 41 warnings generated.================================================================================
Detailed per-defconfig build reports:
allnoconfig (arm64, clang-8) — PASS, 0 errors, 13 warnings, 0 section mismatches
Warnings: <stdin>:1388:2: warning: syscall open_tree not implemented [-W#warnings] #warning syscall open_tree not implemented <stdin>:1391:2: warning: syscall move_mount not implemented [-W#warnings] #warning syscall move_mount not implemented <stdin>:1394:2: warning: syscall fsopen not implemented [-W#warnings] #warning syscall fsopen not implemented <stdin>:1397:2: warning: syscall fsconfig not implemented [-W#warnings] #warning syscall fsconfig not implemented <stdin>:1400:2: warning: syscall fsmount not implemented [-W#warnings] #warning syscall fsmount not implemented <stdin>:1403:2: warning: syscall fspick not implemented [-W#warnings] #warning syscall fspick not implemented 6 warnings generated.
defconfig (arm64, clang-8) — PASS, 0 errors, 68 warnings, 0 section mismatches
Warnings: <stdin>:1388:2: warning: syscall open_tree not implemented [-W#warnings] #warning syscall open_tree not implemented <stdin>:1391:2: warning: syscall move_mount not implemented [-W#warnings] #warning syscall move_mount not implemented <stdin>:1394:2: warning: syscall fsopen not implemented [-W#warnings] #warning syscall fsopen not implemented <stdin>:1397:2: warning: syscall fsconfig not implemented [-W#warnings] #warning syscall fsconfig not implemented <stdin>:1400:2: warning: syscall fsmount not implemented [-W#warnings] #warning syscall fsmount not implemented <stdin>:1403:2: warning: syscall fspick not implemented [-W#warnings] #warning syscall fspick not implemented 6 warnings generated. drivers/soc/rockchip/pm_domains.c:747:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:752:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:752:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:788:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:788:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:789:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:789:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:790:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:790:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:791:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:791:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:792:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:792:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:793:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:793:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:794:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:794:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:795:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:795:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:796:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:796:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:818:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:818:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:818:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:819:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:819:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:819:22: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:820:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:820:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:820:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:821:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:821:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:822:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:822:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:832:20: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:832:20: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:832:20: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:833:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:833:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:834:21: warning: shift count is negative [-Wshift-count-negative] drivers/soc/rockchip/pm_domains.c:834:21: warning: shift count is negative [-Wshift-count-negative] 41 warnings generated. <stdin>:1388:2: warning: syscall open_tree not implemented [-W#warnings] #warning syscall open_tree not implemented <stdin>:1391:2: warning: syscall move_mount not implemented [-W#warnings] #warning syscall move_mount not implemented <stdin>:1394:2: warning: syscall fsopen not implemented [-W#warnings] #warning syscall fsopen not implemented <stdin>:1397:2: warning: syscall fsconfig not implemented [-W#warnings] #warning syscall fsconfig not implemented <stdin>:1400:2: warning: syscall fsmount not implemented [-W#warnings] #warning syscall fsmount not implemented <stdin>:1403:2: warning: syscall fspick not implemented [-W#warnings] #warning syscall fspick not implemented 6 warnings generated.
tinyconfig (arm64, clang-8) — PASS, 0 errors, 13 warnings, 0 section mismatches
Warnings: <stdin>:1388:2: warning: syscall open_tree not implemented [-W#warnings] #warning syscall open_tree not implemented <stdin>:1391:2: warning: syscall move_mount not implemented [-W#warnings] #warning syscall move_mount not implemented <stdin>:1394:2: warning: syscall fsopen not implemented [-W#warnings] #warning syscall fsopen not implemented <stdin>:1397:2: warning: syscall fsconfig not implemented [-W#warnings] #warning syscall fsconfig not implemented <stdin>:1400:2: warning: syscall fsmount not implemented [-W#warnings] #warning syscall fsmount not implemented <stdin>:1403:2: warning: syscall fspick not implemented [-W#warnings] #warning syscall fspick not implemented 6 warnings generated.
For more info write to info@kernelci.org
-- Thanks, ~Nick Desaulniers
From: Matt Hart matthew.hart@linaro.org Date: Thu, May 9, 2019 at 11:08 AM To: Nick Desaulniers Cc: Mark Brown, Arnd Bergmann, Anmar Oueja, Nathan Chancellor, Kernel Build Reports Mailman List, Tri Vo, kernelci.org bot
On Thu, 9 May 2019 at 18:41, Nick Desaulniers ndesaulniers@google.com wrote:
From: kernelci.org bot bot@kernelci.org Date: Wed, May 8, 2019 at 3:38 AM To: natechancellor@gmail.com, broonie@kernel.org, arnd.bergmann@linaro.org, ndesaulniers@google.com, kernel-build-reports@lists.linaro.org, trong@google.com, matthew.hart@linaro.org
next-clang/master build: 4 builds: 1 failed, 3 passed, 94 warnings (next-20190508)
Full Build Summary: https://staging.kernelci.org/build/next-clang/branch/master/kernel/next-2019...
Tree: next-clang Branch: master Git Describe: next-20190508 Git Commit: 31ccad9ba50305d346c6a07760e7ef37686219b9 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Built: 1 unique architecture
Build Failure Detected:
arm64: allmodconfig: (clang-8) FAIL
Any idea what FAIL means? The below 3 builds have their warnings listed, but allmodconfig just says FAIL. Maybe the build timed out?
Hey Nick, doesnt look like the build timed out as it showing in the UI: https://staging.kernelci.org/build/id/5cd2aba2cf3a0f83c38dcaec/
I think whats happened here is the email has not been rendered properly. I'm currently working on a patch that fixes many issues with the build emails (it's why clang builds haven't moved to the production setup yet) and my work-in-progress branch has been merged onto staging recently so there could be some transient errors with emails.
The good news is that the build log is available: http://staging-storage.kernelci.org/next-clang/master/next-20190508/arm64/al...
Oh, right, now I see the error (I thought Rasmus had sent a patch to fix that, maybe it hasn't been picked up into linux-next yet?).
Also, KernelCI can produce a plaintext email (like this one), or a HTML email with clickable links to the build logs, should I switch to the HTML emails so it's easier in future for you to find the log files?
From the line:
Full Build Summary: https://staging.kernelci.org/build/next-clang/branch/master/kernel/next-2019...
it seems like there's lots of builds being done (oh man, lots of red, we'll need to dive deeper into arm32). As long as we have the above link (and I remember to look there), I think we should be fine. It might just take some time for me to learn to effectively navigate kernelci.org. It's awesome; there's so much information. It will just take some time for me to get faster at triage.
On Thu, 9 May 2019 at 19:26, Nick Desaulniers ndesaulniers@google.com wrote:
From: Matt Hart matthew.hart@linaro.org Date: Thu, May 9, 2019 at 11:08 AM To: Nick Desaulniers Cc: Mark Brown, Arnd Bergmann, Anmar Oueja, Nathan Chancellor, Kernel Build Reports Mailman List, Tri Vo, kernelci.org bot
On Thu, 9 May 2019 at 18:41, Nick Desaulniers ndesaulniers@google.com wrote:
From: kernelci.org bot bot@kernelci.org Date: Wed, May 8, 2019 at 3:38 AM To: natechancellor@gmail.com, broonie@kernel.org, arnd.bergmann@linaro.org, ndesaulniers@google.com, kernel-build-reports@lists.linaro.org, trong@google.com, matthew.hart@linaro.org
next-clang/master build: 4 builds: 1 failed, 3 passed, 94 warnings (next-20190508)
Full Build Summary: https://staging.kernelci.org/build/next-clang/branch/master/kernel/next-2019...
Tree: next-clang Branch: master Git Describe: next-20190508 Git Commit: 31ccad9ba50305d346c6a07760e7ef37686219b9 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Built: 1 unique architecture
Build Failure Detected:
arm64: allmodconfig: (clang-8) FAIL
Any idea what FAIL means? The below 3 builds have their warnings listed, but allmodconfig just says FAIL. Maybe the build timed out?
Hey Nick, doesnt look like the build timed out as it showing in the UI: https://staging.kernelci.org/build/id/5cd2aba2cf3a0f83c38dcaec/
I think whats happened here is the email has not been rendered properly. I'm currently working on a patch that fixes many issues with the build emails (it's why clang builds haven't moved to the production setup yet) and my work-in-progress branch has been merged onto staging recently so there could be some transient errors with emails.
The good news is that the build log is available: http://staging-storage.kernelci.org/next-clang/master/next-20190508/arm64/al...
Oh, right, now I see the error (I thought Rasmus had sent a patch to fix that, maybe it hasn't been picked up into linux-next yet?).
Also, KernelCI can produce a plaintext email (like this one), or a HTML email with clickable links to the build logs, should I switch to the HTML emails so it's easier in future for you to find the log files?
From the line:
Full Build Summary: https://staging.kernelci.org/build/next-clang/branch/master/kernel/next-2019...
it seems like there's lots of builds being done (oh man, lots of red,
Yep, sorry I forgot to mention I'd just enabled all the arm32 defconfigs :)
we'll need to dive deeper into arm32). As long as we have the above link (and I remember to look there), I think we should be fine. It might just take some time for me to learn to effectively navigate kernelci.org. It's awesome; there's so much information. It will just take some time for me to get faster at triage.
No worries. The HTML mails are almost identical in layout except the "defconfig (clang-8): 68 warnings" text is a hyperlink to the build log. If you ever do want to switch to those let me know as I can do that per recipient to not force HTML on everyone.
-- Thanks, ~Nick Desaulniers
On Thu, May 09, 2019 at 11:26:39AM -0700, Nick Desaulniers wrote:
From: Matt Hart matthew.hart@linaro.org Date: Thu, May 9, 2019 at 11:08 AM To: Nick Desaulniers Cc: Mark Brown, Arnd Bergmann, Anmar Oueja, Nathan Chancellor, Kernel Build Reports Mailman List, Tri Vo, kernelci.org bot
On Thu, 9 May 2019 at 18:41, Nick Desaulniers ndesaulniers@google.com wrote:
From: kernelci.org bot bot@kernelci.org Date: Wed, May 8, 2019 at 3:38 AM To: natechancellor@gmail.com, broonie@kernel.org, arnd.bergmann@linaro.org, ndesaulniers@google.com, kernel-build-reports@lists.linaro.org, trong@google.com, matthew.hart@linaro.org
next-clang/master build: 4 builds: 1 failed, 3 passed, 94 warnings (next-20190508)
Full Build Summary: https://staging.kernelci.org/build/next-clang/branch/master/kernel/next-2019...
Tree: next-clang Branch: master Git Describe: next-20190508 Git Commit: 31ccad9ba50305d346c6a07760e7ef37686219b9 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Built: 1 unique architecture
Build Failure Detected:
arm64: allmodconfig: (clang-8) FAIL
Any idea what FAIL means? The below 3 builds have their warnings listed, but allmodconfig just says FAIL. Maybe the build timed out?
Hey Nick, doesnt look like the build timed out as it showing in the UI: https://staging.kernelci.org/build/id/5cd2aba2cf3a0f83c38dcaec/
I think whats happened here is the email has not been rendered properly. I'm currently working on a patch that fixes many issues with the build emails (it's why clang builds haven't moved to the production setup yet) and my work-in-progress branch has been merged onto staging recently so there could be some transient errors with emails.
The good news is that the build log is available: http://staging-storage.kernelci.org/next-clang/master/next-20190508/arm64/al...
Oh, right, now I see the error (I thought Rasmus had sent a patch to fix that, maybe it hasn't been picked up into linux-next yet?)
No, it hasn't been. Andrew Morton is sometimes slow to pick some stuff up. We might be able to get Stephen Rothwell to pick them up for -next until Andrew picks them up.
Also, KernelCI can produce a plaintext email (like this one), or a HTML email with clickable links to the build logs, should I switch to the HTML emails so it's easier in future for you to find the log files?
From the line:
Full Build Summary: https://staging.kernelci.org/build/next-clang/branch/master/kernel/next-2019...
it seems like there's lots of builds being done (oh man, lots of red, we'll need to dive deeper into arm32). As long as we have the above link (and I remember to look there), I think we should be fine. It
I'll start looking at it later tonight. Looks like a large majority of them are assembler related.
might just take some time for me to learn to effectively navigate kernelci.org. It's awesome; there's so much information. It will just take some time for me to get faster at triage. -- Thanks, ~Nick Desaulniers
From: Nathan Chancellor natechancellor@gmail.com Date: Thu, May 9, 2019 at 11:38 AM To: Nick Desaulniers Cc: Matt Hart, Mark Brown, Arnd Bergmann, Anmar Oueja, Kernel Build Reports Mailman List, Tri Vo, kernelci.org bot, Rasmus Villemoes
(sorry, gmail is not formatting the above response headers correctly, hopefully a bug in today's build)
On Thu, May 09, 2019 at 11:26:39AM -0700, Nick Desaulniers wrote:
From the line:
Full Build Summary: https://staging.kernelci.org/build/next-clang/branch/master/kernel/next-2019...
it seems like there's lots of builds being done (oh man, lots of red, we'll need to dive deeper into arm32). As long as we have the above link (and I remember to look there), I think we should be fine. It
I'll start looking at it later tonight. Looks like a large majority of them are assembler related.
/usr/bin/as: unrecognized option '-EL'
Something funny is going on with assembler selection, /usr/bin/as is probably the x86 assembler, which won't work for arm.
I thought we had armv7_defconfigs green in our TravisCI runs? https://travis-ci.com/ClangBuiltLinux/continuous-integration/builds/11116730...
I wonder if the build machines maybe don't have arm-linux-gnueabihf-as (or arm-linux-gnueabihf-binutils package) installed on them? Matt, can you confirm?
I should send Masahiro a patch to Kbuild that checks that these actually exist, and fail with an actionable error message saying something like "yo, I couldn't find the assembler you told me to use, what are you doing?" rather than "oh I didn't recognize this flag (cause it's for arm and I'm x86)."
On Thu, 9 May 2019 at 20:08, Nick Desaulniers ndesaulniers@google.com wrote:
From: Nathan Chancellor natechancellor@gmail.com Date: Thu, May 9, 2019 at 11:38 AM To: Nick Desaulniers Cc: Matt Hart, Mark Brown, Arnd Bergmann, Anmar Oueja, Kernel Build Reports Mailman List, Tri Vo, kernelci.org bot, Rasmus Villemoes
(sorry, gmail is not formatting the above response headers correctly, hopefully a bug in today's build)
On Thu, May 09, 2019 at 11:26:39AM -0700, Nick Desaulniers wrote:
From the line:
Full Build Summary: https://staging.kernelci.org/build/next-clang/branch/master/kernel/next-2019...
it seems like there's lots of builds being done (oh man, lots of red, we'll need to dive deeper into arm32). As long as we have the above link (and I remember to look there), I think we should be fine. It
I'll start looking at it later tonight. Looks like a large majority of them are assembler related.
/usr/bin/as: unrecognized option '-EL'
Something funny is going on with assembler selection, /usr/bin/as is probably the x86 assembler, which won't work for arm.
I thought we had armv7_defconfigs green in our TravisCI runs? https://travis-ci.com/ClangBuiltLinux/continuous-integration/builds/11116730...
I wonder if the build machines maybe don't have arm-linux-gnueabihf-as (or arm-linux-gnueabihf-binutils package) installed on them? Matt, can you confirm?
The build container is built from this: https://github.com/kernelci/kernelci-core/blob/master/jenkins/dockerfiles/cl...
So yes, looks like it only has binutils-aarch64-linux-gnu installed, and we need binutils-arm-linux-gnueabihf from debian as well.
I'll just check before I put up a PR, that installing the extra package wont break arm64 builds.
I should send Masahiro a patch to Kbuild that checks that these actually exist, and fail with an actionable error message saying something like "yo, I couldn't find the assembler you told me to use, what are you doing?" rather than "oh I didn't recognize this flag (cause it's for arm and I'm x86)." -- Thanks, ~Nick Desaulniers
On Thu, 9 May 2019 at 20:08, Nick Desaulniers ndesaulniers@google.com wrote:
I should send Masahiro a patch to Kbuild that checks that these actually exist, and fail with an actionable error message saying something like "yo, I couldn't find the assembler you told me to use, what are you doing?" rather than "oh I didn't recognize this flag (cause it's for arm and I'm x86)."
https://lkml.org/lkml/2019/5/9/969
https://github.com/kernelci/kernelci-core/pull/67
From: Nick Desaulniers ndesaulniers@google.com Date: Thu, May 9, 2019 at 1:20 PM To: Matt Hart Cc: Nathan Chancellor, Mark Brown, Arnd Bergmann, Anmar Oueja, Kernel Build Reports Mailman List, Tri Vo, kernelci.org bot, Rasmus Villemoes, clang-built-linux
On Thu, 9 May 2019 at 20:08, Nick Desaulniers ndesaulniers@google.com wrote:
I should send Masahiro a patch to Kbuild that checks that these actually exist, and fail with an actionable error message saying something like "yo, I couldn't find the assembler you told me to use, what are you doing?" rather than "oh I didn't recognize this flag (cause it's for arm and I'm x86)."
https://lkml.org/lkml/2019/5/9/969
-- Thanks, ~Nick Desaulniers
kernel-build-reports@lists.linaro.org
-
kernelci.org bot -
Matt Hart -
Nathan Chancellor -
Nick Desaulniers