rpms/llvm
7
0
Fork 0
mirror of https://src.fedoraproject.org/rpms/llvm.git synced 2024-11-28 10:35:42 +00:00
Code Issues 5 Projects Releases Packages Wiki Activity Actions
llvm/tests/build-gating.fmf

92 lines
2.8 KiB
Text
Raw Normal View History

tests: add support for SCL-ized LLVM 13 (llvm-toolset-13.0)
2021-12-06 08:34:51 +00:00
#
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-10-22 09:14:45 +00:00
# Build/PR gating tests for *LLVM 19*
tests: add support for SCL-ized LLVM 13 (llvm-toolset-13.0)
2021-12-06 08:34:51 +00:00
#
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-10-22 09:14:45 +00:00
# Compatible with various LLVM 19 distributions:
tests: add support for SCL-ized LLVM 13 (llvm-toolset-13.0)
2021-12-06 08:34:51 +00:00
#
# * Fedora (ursine packages)
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-10-22 09:14:45 +00:00
# * CentOS 10 stream (ursine packages)
tests: add support for SCL-ized LLVM 13 (llvm-toolset-13.0)
2021-12-06 08:34:51 +00:00
# * Centos 9 stream (ursine packages)
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-10-22 09:14:45 +00:00
# * RHEL-10 (ursine packages)
tests: add support for SCL-ized LLVM 13 (llvm-toolset-13.0)
2021-12-06 08:34:51 +00:00
# * RHEL-9 (ursine packages)
# * RHEL-8 (Red Hat module)
#
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-12 12:52:36 +00:00
summary: LLVM tests for build/PR gating
adjust:
- because: "Plan to be ran when either executed locally, or executed by CI system to gate a build or PR."
when: >-
trigger is defined
and trigger != commit
and trigger != build
enabled: false
tests: add support for SCL-ized LLVM 13 (llvm-toolset-13.0)
2021-12-06 08:34:51 +00:00
- because: "When testing SCL-ized LLVM, the collection must be enabled first"
environment+:
WITH_SCL: "scl enable llvm-toolset-13.0 rust-toolset-1.58"
when: "collection == llvm-toolset-13.0"
tests: add llvm-toolset-14.0 requirements to tests and plans
2022-04-22 11:04:50 +00:00
- because: "When testing SCL-ized LLVM, the collection must be enabled first"
environment+:
WITH_SCL: "scl enable llvm-toolset-14.0 rust-toolset-1.62"
when: "collection == llvm-toolset-14.0"
tests: add support for SCL-ized LLVM 13 (llvm-toolset-13.0)
2021-12-06 08:34:51 +00:00
tests: CRB in CentOS has different name
2022-02-03 11:39:48 +00:00
# Unfortunatelly, TMT does not support more declarative approach, we need to run commands on our own.
- because: "On CentOS, CRB must be enabled to provide rarer packages"
prepare+:
- name: Enable CRB
how: shell
script: dnf config-manager --set-enabled crb
when: >-
distro == centos
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 13:50:08 +00:00
# Unfortunately, TMT does not support more declarative approach, we need to run commands on our own.
tests: add extra repositories to allow installation of ninja/libstdc++
2021-12-15 12:03:43 +00:00
- because: "On RHEL, CRB must be enabled to provide rarer packages"
prepare+:
- name: Enable CRB
how: shell
script: dnf config-manager --set-enabled rhel-CRB
when: >-
tests: CRB in CentOS has different name
2022-02-03 11:39:48 +00:00
distro == rhel-9
tests: add extra repositories to allow installation of ninja/libstdc++
2021-12-15 12:03:43 +00:00
or distro == rhel-8
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-12 12:52:36 +00:00
discover:
Migrate tests to tests/llvm repo
2022-09-12 11:18:15 +00:00
- name: llvm-tests
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-12 12:52:36 +00:00
how: fmf
Migrate tests to tests/llvm repo
2022-09-12 11:18:15 +00:00
url: https://src.fedoraproject.org/tests/llvm.git
ref: main
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-10-22 09:14:45 +00:00
filter: "tag:-spoils-installation & tag:-not-in-default"
- name: clang-tests
how: fmf
url: https://src.fedoraproject.org/tests/clang.git
ref: main
filter: "tag:-spoils-installation & tag:-not-in-default"
- name: compiler-rt-tests
how: fmf
url: https://src.fedoraproject.org/tests/compiler-rt.git
ref: main
filter: "tag:-spoils-installation & tag:-not-in-default"
- name: libomp-tests
how: fmf
url: https://src.fedoraproject.org/tests/libomp.git
ref: main
filter: "tag:-spoils-installation & tag:-not-in-default"
- name: python-lit
how: fmf
url: https://src.fedoraproject.org/tests/python-lit.git
ref: main
filter: "tag:-spoils-installation & tag:-not-in-default"
- name: lld-tests
how: fmf
url: https://src.fedoraproject.org/tests/lld.git
ref: main
filter: "tag:-spoils-installation & tag:-not-in-default"
- name: lldb-tests
how: fmf
url: https://src.fedoraproject.org/tests/lldb.git
ref: main
filter: "tag:-spoils-installation & tag:-not-in-default"
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-12 12:52:36 +00:00
execute:
how: tmt
provision:
hardware:
memory: ">= 4 GiB"
Reference in a new issue Copy permalink