This change makes it so that the builder takes a list of standard versions to test against. The default list is just c++11. For each standard on the list a job is added.
This also changes the builder so it invokes LIT directly for libcxx instead of using check-libcxx.
Details
- Reviewers
danalbert gribozavr gkistanova
Diff Detail
Event Timeline
Could we add more targets instead, check-libcxx-cxx11, check-libcxx-cxx14 etc?
Then it would be easier to run them when developing libcxx itself.
I agree that we should add these Makefile targets, but I would like to keep invoking lit directly in this change for a couple of reasons:
- We need a custom LIT invocation so the output is more "log" friendly (no progress bar).
- More changes are going to follow that require custom invocations. (Testing debug mode, sanitizers, ect)
- I don't want to add the makefile targets until I've actually added support for running the tests as C++03, C++14, ect. So I want to use the bots to test these changes.
If you don't have any strong objections I would like to keep the custom LIT invocations.
zorg/buildbot/builders/LibcxxAndAbiBuilder.py | ||
---|---|---|
95 | '-s` add the progress bar that is non-log friendly. I'll add -s and --no-progress-bar, but I'm personally not opposed to printing the passing tests. | |
99 | I'm not actually sure, but I also don't think the working dir matters that much anyway. I'll remove it. |
-s so we're not inundated with all the passing tests?