From b72203bcdbc99b8a972faa088d187165c948a6ac Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?V=C3=A1clav=20Kadl=C4=8D=C3=ADk?= <vkadlcik@redhat.com>
Date: Mon, 2 Jun 2025 13:14:13 +0200
Subject: [PATCH] Tune testing setup

- 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)
---
 plans/tier0.fmf |  2 ++
 rpminspect.yaml | 23 +++++++++++++++++++++++
 2 files changed, 25 insertions(+)
 create mode 100644 rpminspect.yaml

diff --git a/plans/tier0.fmf b/plans/tier0.fmf
index 13f8bcb..f184c31 100644
--- a/plans/tier0.fmf
+++ b/plans/tier0.fmf
@@ -8,6 +8,8 @@
 #   trigger=build
 ---
 summary: Tier 0 test plan
+context:
+  component: gcc-toolset-15-gcc
 environment+:
   WITH_SCL: gcc-toolset-15-env
 discover:
diff --git a/rpminspect.yaml b/rpminspect.yaml
new file mode 100644
index 0000000..f20f2f5
--- /dev/null
+++ b/rpminspect.yaml
@@ -0,0 +1,23 @@
+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