.fmf/version

@@ -0,0 +1 @@
+1

.gcc-toolset-13-gcc.metadata

@@ -1,4 +0,0 @@
-e1fb4ded21712a1724ce05b86ff738ee6d21256c SOURCES/gcc-13.3.1-20240611.tar.xz
-ae5fbb33bcb442121fbbf482a93f6b3c84d489ee SOURCES/isl-0.24.tar.bz2
-003af8bc05476507f4dd02340b727b72b404e275 SOURCES/newlib-cygwin-9e09d6ed83cce4777a5950412647ccc603040409.tar.xz
-6bfe7ac1b208935ee2c0939bb47cfe775c1c81b3 SOURCES/nvptx-tools-aa3404ad5a496cda5d79a50bedb1344fd63e8763.tar.xz

.gitignore

@@ -1,4 +1,4 @@
-SOURCES/gcc-13.3.1-20240611.tar.xz
-SOURCES/isl-0.24.tar.bz2
-SOURCES/newlib-cygwin-9e09d6ed83cce4777a5950412647ccc603040409.tar.xz
-SOURCES/nvptx-tools-aa3404ad5a496cda5d79a50bedb1344fd63e8763.tar.xz
+/gcc-13.1.1-20230614.tar.xz
+/gcc-13.2.1-20231205.tar.xz
+/gcc-13.3.1-20240522.tar.xz
+/gcc-13.3.1-20240611.tar.xz

gating.yaml

@@ -0,0 +1,6 @@
+--- !Policy
+product_versions:
+  - rhel-8
+decision_context: osci_compose_gate
+rules:
+  - !PassingTestCaseRule {test_case_name: baseos-ci.brew-build.tier1.functional}

rpminspect.yaml

@@ -0,0 +1,22 @@
+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 are not
+    # 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-13/root/usr/lib64
+      - /opt/rh/gcc-toolset-13/root/usr/lib

sources

@@ -0,0 +1,4 @@
+SHA512 (gcc-13.3.1-20240611.tar.xz) = 4cf86cf58663e89b54198824eaf6387157f8fb205f700815d8066150f393ceecb41f3f369c772e5855a4555eccf24c5dfd501507337d0438cc8134d0df02f696
+SHA512 (isl-0.24.tar.bz2) = aab3bddbda96b801d0f56d2869f943157aad52a6f6e6a61745edd740234c635c38231af20bc3f1a08d416a5e973a90e18249078ed8e4ae2f1d5de57658738e95
+SHA512 (newlib-cygwin-9e09d6ed83cce4777a5950412647ccc603040409.tar.xz) = bef3fa04f7b1a915fc1356ebed114698b5cc835e9fa04b0becff05a9efc76c59fb376482990873d222d7acdcfee3c4f30f5a4cb7f3be1f291f1fa5f1c7a9d983
+SHA512 (nvptx-tools-aa3404ad5a496cda5d79a50bedb1344fd63e8763.tar.xz) = 33a024326426375533cb5dd9b68b2508f37540be418d2506bfa19a5f5866485e9af150469064e9059b68136ad8cb080b3b12e7eb5c6b7d1288cf6bfb3f6bb5d0

tier0.fmf

@@ -0,0 +1,39 @@
+# Tier 0 test plan. It's actually Tier 1
+#   - limited to its public part
+#   - executed on the architecture at hand
+# When run by osci.tier0 on CentOS Stream or RHEL, it receives the following
+# context:
+#   arch=x86_64 (the architecture at hand, currently OSCI uses just x86_64)
+#   distro=rhel<M>.<m> (even for CentOS Stream builds)
+#   trigger=build
+---
+summary: Tier 0 test plan
+context:
+  collection: gcc-toolset-13
+environment+:
+  COLLECTIONS: gcc-toolset-13
+  WITH_SCL: "scl enable gcc-toolset-13"
+discover:
+  - name: collect_info
+    how: shell
+    tests:
+      - name: /info/rpms
+        test: rpm -qa --last
+  - name: public_tests
+    how: fmf
+    url: https://gitlab.com/redhat/centos-stream/tests/gcc.git
+    filter: 'tag: CI-Tier-1'
+provision+:
+  hardware:
+    disk:
+      - size: ">= 60 GiB"
+    memory: ">= 8 GiB"
+prepare+:
+  - how: shell
+    script:
+      - dnf config-manager --set-enabled '*CRB*' || true
+      - dnf config-manager --set-enabled crb || true
+      - dnf config-manager --set-enabled rhel-buildroot || true
+      - dnf config-manager --set-enabled epel || true
+execute:
+  how: tmt