Add a new sanitizer bot. The host compiler is clang fixed at a specific
revision; it will not be rebuilt unless the revision number is changed in the
bot config. The host compiler does incremental builds of (A,M)San-instrumented
LLVM/clang, which are then tested with check-llvm, check-clang.
Details
Diff Detail
Event Timeline
buildbot/osuosl/master/config/slaves.py | ||
---|---|---|
161 | No idea what "jobs" does. |
mostly looks great
zorg/buildbot/builders/sanitizers/buildbot_bootstrap_lite.sh | ||
---|---|---|
2 ↗ | (On Diff #17354) | This it not bootstrap at all, I'd prefer another name (fast-sanitizer-build?). |
zorg/buildbot/builders/sanitizers/buildbot_bootstrap_lite.sh | ||
---|---|---|
2 ↗ | (On Diff #17354) | You're right. How about sanitizer-x86_64-linux-fast? |
Another thing I don't understand is how fatal and non-fatal steps are configured. I.e. here:
http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/14600
we fail to build the host compiler, so all remaining steps are skipped. On the other hand, when a test fails, we still run the remaining steps:
http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap/builds/5327
Yet, it looks like in both cases the script looks exactly the same:
(run_step) || echo @@@STEP_FAILURE@@@
No, in the first case the line is:
(cd clang_build && cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo \
${CMAKE_COMMON_OPTIONS} $LLVM_CHECKOUT)
And the script sets "-e", so a non-zero exit code in this line is fatal.
This could be made more consistent.
But then we have:
(cd clang_build && make clang -j$MAKE_JOBS) || echo @@@STEP_FAILURE@@@
So a cmake failure is fatal, but a build failure is not. Ugh!
No idea what "jobs" does.