Project

General

Profile

Actions

action #66664

closed

circleci jobs do not retry, are aborted with "Too long with no output (exceeded 10m0s): context deadline exceeded"

Added by okurz over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2020-05-09
Due date:
% Done:

0%

Estimated time:

Description

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 extend that limit. Maybe there is a circleCI configuration variable for that?

Related issues 3 (0 open3 closed)

Related to openQA Project - action #71464: Show output of failed tests within circleci log view, like on local prove calls, not only "Tests" tabResolvedokurz2020-09-17

Actions
Related to openQA Infrastructure - action #152941: circleCI job runs into 20m timeout due to slow download from registry.opensuse.orgResolvedokurz2023-12-27

Actions
Copied to openQA Project - action #71467: add specific timeout values to all applicable openQA tests in t/Resolvedokurz

Actions
Actions

Also available in: Atom PDF