CI fails if test file contains the word "unexpected" or "unresolved"

[CohenArthur]

#2373 is failing because @MahadMuhammad added a testfile named "unexpected_arguments.rs". This is a funny behavior but it would be nice not to have it haha.

https://github.com/Rust-GCC/gccrs/actions/runs/5465722215/jobs/9949574002?pr=2373

[CohenArthur]

This is also happening in #2383

[tschwinge]

Yeah, we should use a better method for detecting regressions than the current grep unexpected etc.

..., but I don't know yet how to properly do that. (I always diff before/after *.sum files, but that's not applicable for this CI system.)

[dkm]

Yeah, we should use a better method for detecting regressions than the current grep unexpected etc.

..., but I don't know yet how to properly do that. (I always diff before/after *.sum files, but that's not applicable for this CI system.)

There's also the ./contrib/dg-cmp-results.sh that is nice for this task.

As a bandaid, we could match # unexpected ..., as it's done in the bootstrap workflow. Or is there a reason why we can't?

[CohenArthur]

Yeah I think we could definitely look for # of {unexpected,unresolved} instead. Can't think of a reason why not