https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116260
Thiago Jung Bauermann <thiago.bauermann at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |clyon at gcc dot gnu.org
--- Comment #1 from Thiago Jung Bauermann <thiago.bauermann at linaro dot org>
---
Hello Sam,
I mostly work with the GDB testsuite, so I'm not very familiar with
GCC-specific details of DejaGNU and the sum files, so advance warning:
naive questions ahead.
I added Christophe Lyon to the Cc list. He's much more familiar with the
GCC testsuite and how we use it.
(In reply to Sam James from comment #0)
> 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.
Nice!
> I tried wiring up multilib tests next in our packaging and noticed that the
> manifest ended up mixing results between ABIs, like:
I'm not sure I understand the scenario. Are you doing two testsuite runs,
one for each ABI, and then using the one's manifest to compare with the
other?
> dejagnu emits lines indicating which ABI tests were run for,
Do you mean these lines?
```
Native configuration is armv8l-unknown-linux-gnueabihf
=== gcc tests ===
Schedule of variations:
tcwg-local
Running target tcwg-local
```
> 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?
It's possible to add an ABI field to the ResultSet object and then use it
when comparing results.
