As part of tier0 unification across the rhel-pt-gcc components
(RHEL-113756), introduce tier0 testing. The testing is limited
to x86_64-only (OSCI-imposed).
The tests selected for it are the public part of tier1. In other
words, we are introducing tier0 as a subset of tier1, run on
x86_64-only.
For awareness, RHEL builds get full tier1 in a later phase of
gating (BaseOS CI). This commit doesn't affect that in any way;
now we are just adding a small bit of functional testing sooner
in the pipeline.
The tier1 tests were traditionally run by BaseOS CI by various
tasks if the baseos-ci.brew-build.* family, typically implemented
by Beaker jobs.
Every component used to have its own special flavor of the
configuration, both in BaseOS CI (the triggering part) and here in
the component's gating.yaml (results processing).
The each-component-is-a-snowflake approach didn't work very well,
creating discrepancies like RHEL-140879.
At long last, I've unified the BaseOS CI configuration for all my
components:
- drop the Beaker job(s) (which have been declared obsoleted anyway)
- trigger two OpenStack jobs
- "fast lane" for architectures where we usually get results fast,
sometimes it's advantageous to take a look ASAP
- "slow lane" for architectures we typically have to wait
For reference, it's commit d2baef686 in baseos-qe/citool-config.
Now I'm fixing the counterpart in gating.yaml (results processing):
We wait for the "fast lane" and "slow lane" results and they both
must pass.
Handle this:
Spec filename does not exactly match the primary name
gcc-toolset-14-annobin; got 'annobin.spec'
The spec file name does not match the expected NAME.spec
format. Rename the spec file to conform to this policy.
