b72203bcdb
- Bring the same rpminspect configuration we already have in older
RHELs. We'll need it.
- Inject component=gcc-toolset-15-gcc as a new context item into tmt
testing. The reason:
On the old times ("SCL" times) we were able to recognize
GCC Toolset builds and adjust individual test thanks to mere
existence of the "collection=gcc-toolset-<NN>" item in the context.
For SCL-less GCC Toolsets it's no longer possible. Therefore we
need:
- inject the new context item here (and all other downstream plans
which is however out of scope of this commit)
- update the metadata in all the downstream tests that adjust
themselves depending on the "collection" item in the context
(this again is out of scope here)
24 lines
869 B
YAML
24 lines
869 B
YAML
badfuncs:
|
|
# GCC doesn't use the "forbidden" functions as such. Just some of its
|
|
# sanitizers can instrument those functions which leads to false
|
|
# positives in the badfuncs test.
|
|
ignore:
|
|
- /usr/lib*/libasan.so.*.*.*
|
|
- /usr/lib*/libtsan.so.*.*.*
|
|
|
|
specname:
|
|
# In GCC toolsets builds, the spec file name and the package may not
|
|
# be exactly the same, the package is prefixed with gcc-toolset-NN-.
|
|
# Let's ignore the prefix.
|
|
match: suffix
|
|
primary: filename
|
|
|
|
runpath:
|
|
# Although gcc-toolset sanitizers link gcc-toolset libraries from
|
|
# /opt/..., they themselves are placed in /usr. The runpath test
|
|
# doesn't like this difference. Explicitly allow it.
|
|
allowed_paths:
|
|
- /opt/rh/gcc-toolset-15/root/usr/lib
|
|
- /opt/rh/gcc-toolset-15/root/usr/lib/../lib64
|
|
- /opt/rh/gcc-toolset-15/root/usr/lib64
|