My expectation is that in the future, more tests will land in this git,
and not all of them would be useful in gating time. AFAIK, CI systems do
run everything they can, therefore adding `when` to control when the
plan is executed - `is not defined` bit should allow anyone to run it
manually, while the rest of the condition should limit its presence to
gating events.
This was originally stored in provision.fmf, but after the TMT
transition, this information should be preserved. It is probably not
honoured by that many CI systems, but things will get better over time.
See https://tmt.readthedocs.io/en/stable/spec/plans.html#hardware for
specification details.
* tests.yml => tests-llvm.yml, to allow composition by "dumping" tests
from several LLVM components when testing a module or collection;
* more comments, to highlight part where downstream maintaners and QEs
need to modify tests;
* fixed failing tests to get a clean table as a verification tests do
work after my changes.
There is a bug in the build system that can cause binary stripping
to fail without failing the build, so add a check to ensure that
libLLVM.so is stripped.
https://bugzilla.redhat.com/show_bug.cgi?id=1793250
Also replace %global compat_build 0 with %bcond_with compat_build.
This will make it easier to test building the compat version of the
package and allow us to add a CI test for it.
- Add some missing Requires
- Add --threads option to run-lit-tests script
- Set PATH so lit can find tools like count, not, etc.
- Don't hardcode tools directory to /usr/lib64/llvm
- Fix typo in yaml-bench define
- Only print information about failing tests
- Run tests in CI with only 1 thread
