Test ocamlbuild on Travis CI #172
Conversation
This is preparing ground for a future commit where the testsuite can link plugins from a non-installed ocamlbuild tree.
This results in spurious rebuilds and broken parallel builds.
Before this commit, it was very easy to accidentally use artifacts
from the installed ocamlbuild instance. In fact, it was impossible
to test linking of plugins properly, because plugins were always
linked with the system ocamlbuildlib.cm{x,}a.
After this commit, the testsuite does not need any user action
to use the correct ocamlbuild executable or ocamlbuildlib.cm{x,}a.
A specific testsuite can be invoked with `make test-NAME` (where NAME is currently one of internal, findlibonly, external), and every testsuite can be invoked with `make test`. Also, any failing test now sets the exit status of the testsuite to 1.
|
No objection at all in principle. I had the impression that I saw a preliminary version of this PR with only the |
|
(There is this mesmerizing "Some checks haven't completed yet" that makes me want to wait, but feel free to merge now, or I'll do it when I see the CI result.) |
|
So the test fails, of course, given that mtime fails. @whitequark is it your intention to have a failing CI as long as your fixing PR is not merged or the change reverted, or should we temporarily disable the |
You've seen that. I rebase a lot, in general. Keeps the history clean.
That is my intention indeed, because master is broken right now. No reason to hide that status. |
2 participants
No description provided.