action #66664
Updated by okurz over 3 years ago
## Observation See https://app.circleci.com/pipelines/github/os-autoinst/openQA/2816/workflows/c00e8812-3cc0-4d07-ab9b-f2d5092a6704/jobs/26595/steps and https://app.circleci.com/pipelines/github/os-autoinst/openQA/2817/workflows/1553c384-dbef-48a9-9b3a-91dc2a6477d8/jobs/26605/steps . Tests get stuck within the 1st of 3 retries and are aborted with "Too long with no output (exceeded 10m0s): context deadline exceeded". Maybe processes left over in the background? ## Acceptance criteria * **AC1:** The test output within circle CI reveals the real problem, not just "context deadline exceeded" ## Suggestions * Research about circleci meaning of "context deadline exceeded" * Create artificial test run that can trigger this problem * Try with applying timeout values within individual test modules that are in sum smaller than the global time limit of 10m, e.g. with `use OpenQA::Test::TimeLimit '20';` * Or 10m or extend that limit. Maybe there is a circleCI configuration variable for that?