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