This does not change the behavior directly: the tests only run when
-DMLIR_INCLUDE_INTEGRATION_TESTS=ON is configured. However running
ninja check-mlir will not run all the tests within a single
lit invocation. The previous behavior would wait for all the integration
tests to complete before starting to run the first regular test. The
test results were also reported separately. This change is unifying all
of this and allow concurrent execution of the integration tests with
regular non-regression and unit-tests.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
No the long pause is usually due to the "standalone" test in the examples which runs CMake before building. You can avoid this by not configuring with -DLLVM_INCLUDE_EXAMPLES=ON
What this changes in practice is this:
$ ninja check-mlir 4.494 [3/3/215] Running the MLIR integration tests Testing Time: 45.39s Unsupported: 1 Passed : 80 60.002 [0/1/220] Running the MLIR regression tests Testing Time: 5.42s Unsupported: 45 Passed : 742
Becomes :
$ ninja check-mlir 0.000 [0/1/0] Running the MLIR regression tests Testing Time: 44.86s Unsupported: 46 Passed : 822
Would you please post a note on this on the original discourse thread in which I proposed adding the integration tests (the discussion there was in favor of moving this out of test), just so that when people find that thread, they are not confused why it is no longer there.
Thanks for posting on discourse. Yes, this change makes a lot of sense, unifying the test (when configured).
Thanks for making the change!
I just had submitted two minor changes to the integration test, that probably conflicts with this.
Sorry about that, let me know if you need a pointer on what I changed.