Intermittent E2E test failure: ERROR: 1 setup jobs failed. Check logs above for details #3796
Comments
|
/assign |
|
Hi @wallrj! I am relatively new to writing bash scripts so just wanted to confirm a few things:
Would this be recommended over the first approach? I can see that the benefit of this would be that we'll be able to see all the jobs that fail in a single test run. But the downside would be that if we know that one job has failed, we know the entire test will fail so we would be using unnecessary resources running all other jobs.
Thanks! |
|
/priority important-soon |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The E2E tests sometimes fail during setup with the message:
-- https://prow.build-infra.jetstack.net/view/gcs/jetstack-logs/pr-logs/pull/jetstack_cert-manager/3647/pull-cert-manager-e2e-v1-20/1359494849920765955#1:build-log.txt%3A668 (thanks @irbekrm )
The setup jobs are launched as background shell jobs:
But the logs of all the setup jobs are mixed up, so it's difficult to know which job failed and what went wrong.
Simplest solution would be to disable the parallelism and run the setup jobs in series.
Alternatively we might try and keep track of exactly which jobs failed and show the logs of those jobs on failure.
And that should allow us to find out which of the jobs keeps failing.
/kind flake
/cc @RinkiyaKeDad
The text was updated successfully, but these errors were encountered: