Commit graph

8 commits

Author SHA1 Message Date
Jesus Checa Hidalgo
0b028e44fc Update build-gating plan to test all components
With the merge of all the packages into llvm now we need to test
all those with llvm, but the tests are still scattered across different
test repos. This commit adds discover steps to gather all the tests.
2024-11-21 14:55:34 +01:00
Jesus Checa Hidalgo
2ce66b7035 Migrate tests to tests/llvm repo 2022-09-19 14:28:26 +00:00
Jesus Checa Hidalgo
18f0d9a072 tests: do not use ninja-build for integration testsuite
ninja-build is distributed from extra repos such as epel.
Unfortunately this is not available in all supported archs
which makes it impossible to test with ninja-build.
2022-05-04 15:50:16 +02:00
Jesus Checa Hidalgo
965c7fbf2c tests: add llvm-toolset-14.0 requirements to tests and plans 2022-04-22 13:04:50 +02:00
Miloš Prchlík
e6d1a04f09 tests: CRB in CentOS has different name 2022-02-03 14:33:55 +01:00
Miloš Prchlík
f97fd4bb29 tests: add extra repositories to allow installation of ninja/libstdc++ 2022-01-11 16:01:30 +00:00
Miloš Prchlík
978f4952dd tests: add support for SCL-ized LLVM 13 (llvm-toolset-13.0) 2021-12-13 12:29:21 +01:00
Milos Prchlik
6564e5278d tests: rename default plan to build-gating to better eflect its current purpose
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.
2021-11-16 16:26:59 +01:00