[llvm-dev] Buildbots do not detect test-suite failures!!! (original) (raw)
Nemanja Ivanovic via llvm-dev llvm-dev at lists.llvm.org
Thu Feb 14 03:30:32 PST 2019
- Previous message: [llvm-dev] [Job Ad] IBM is hiring compiler engineers
- Next message: [llvm-dev] Debugging Compiler-RT code
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
It has just been brought to my attention that our buildbots no longer report failures to compile/link files in the test-suite as failures for the build. As a result, we have at least one bot that is currently showing a green status, yet it aborts when building 3 test cases.
I assume that something has changed with how (presumably LNT) reports these failures and the Zorg code does not adequately detect this (I think the buildbot scripts grep for a string such as "FAIL:" in the log or something along those lines). Previously, a failure to compile would show up as two failures (a failure at compile time and a failure at link time). Now it just shows up as NOEXE.
This really seems like something we should fix ASAP.
For an example: http://lab.llvm.org:8011/builders/clang-s390x-linux-lnt/builds/11252/steps/test-suite/logs/stdio
The Vector-build test case shows up as NOEXE and we're clearly hitting an UNREACHABLE while compiling the test:
Unexpected node to lower UNREACHABLE executed at ... -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190214/86edfdc7/attachment.html>
- Previous message: [llvm-dev] [Job Ad] IBM is hiring compiler engineers
- Next message: [llvm-dev] Debugging Compiler-RT code
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]