https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116260
Bug ID: 116260
Summary: testsuite-management/validate_failures.py: split
multilib ABIs in results
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: sjames at gcc dot gnu.org
Target Milestone: ---
We've started using validate_failures.py in our packaging (and I'm using it in
my own workflow too) and it's great, thanks for it.
I tried wiring up multilib tests next in our packaging and noticed that the
manifest ended up mixing results between ABIs, like:
```
diff --git a/x86_64-pc-linux-gnu/15/x86_64-pc-linux-gnu.xfail
b/x86_64-pc-linux-gnu/15/x86_64-pc-linux-gnu.xfail
index ce547e8..44e3d82 100644
--- a/x86_64-pc-linux-gnu/15/x86_64-pc-linux-gnu.xfail
+++ b/x86_64-pc-linux-gnu/15/x86_64-pc-linux-gnu.xfail
@@ -6,6 +6,9 @@ FAIL: c52104x
=== g++ tests ===
Running g++:/gcc/testsuite/g++.dg/analyzer/analyzer.exp ...
+FAIL: c-c++-common/analyzer/asm-x86-dyndbg-2.c -std=c++17 (test for excess
errors)
+FAIL: c-c++-common/analyzer/asm-x86-dyndbg-2.c -std=c++26 (test for excess
errors)
+FAIL: c-c++-common/analyzer/asm-x86-dyndbg-2.c -std=c++98 (test for excess
errors)
FAIL: c-c++-common/analyzer/error-uninit.c -std=c++17 (test for excess errors)
FAIL: c-c++-common/analyzer/error-uninit.c -std=c++26 (test for excess errors)
FAIL: c-c++-common/analyzer/error-uninit.c -std=c++98 (test for excess errors)
@@ -86,6 +89,9 @@ FAIL: c-c++-common/Wrestrict-2.c -std=gnu++98 strncpy (test
for warnings, line 8
FAIL: c-c++-common/attr-nonstring-3.c -std=gnu++17 (test for excess errors)
FAIL: c-c++-common/attr-nonstring-3.c -std=gnu++26 (test for excess errors)
FAIL: c-c++-common/attr-nonstring-3.c -std=gnu++98 (test for excess errors)
+FAIL: c-c++-common/musttail12.c -std=c++11 (test for excess errors)
+FAIL: c-c++-common/musttail12.c -std=c++17 (test for excess errors)
+FAIL: c-c++-common/musttail12.c -std=c++26 (test for excess errors)
[...]
```
dejagnu emits lines indicating which ABI tests were run for, could
validate_failures.py handle that and either have a way to ignore for a given
ABI so it can be re-run with another (from the same testsuite results dir), or
parse those lines and output some suffixed manifest file?
