Skip to content

Conversation

@sawenzel
Copy link
Contributor

No description provided.

@github-actions
Copy link

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

* ability to just wait for any succeeding job in a split
* some cleanup/renaming
Provides
* Template file to generate anchored MC jobs
* A driver script creating actual test jobs and executing them on the GRID
* CSV data file specifying which software tags should be tested

The idea is that this should be used to check if
MC (daily) releases are compatible with the 2tag approach relative
to a given set of async software releases.
@sawenzel sawenzel force-pushed the swenzel/2tag_testing branch from cac8e8f to 15d2c67 Compare August 7, 2025 09:45
@sawenzel sawenzel merged commit e0cf052 into AliceO2Group:master Aug 7, 2025
6 of 7 checks passed
@sawenzel sawenzel deleted the swenzel/2tag_testing branch August 7, 2025 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant