Optionally ignore some E2E test failures to let new tests bake about testing HOT 5 CLOSED

It's not easy to tell whether a failure in junit file should be ignored or not.

from testing.

Why does that matter? We only want the ignore to apply to the GitHub status check that prow reports so that we can mark a test as not blocking merges.

The GitHub status check is based on the exit code which we compute in run_e2e_workflow.py based on

• Did argo workflows succeed
• Were there any junit files with failures

So our config file would just have to allow us to ignore an argo workflow and junit file when computing the exit code.

Might be nice if we could put some metadata into junit files that would specify which workflow generated them.

from testing.

Yes we need that metadata to tell whether a junit file can be ignored.

from testing.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in one week if no further activity occurs. Thank you for your contributions.

from testing.

This issue has been closed due to inactivity.

from testing.