Project

General

Profile

Actions

action #80800

closed

flaky/unstable t/full-stack.t, Failed test 'test 1 is running', Bailout called. Further testing stopped: URL for os-autoinst cmd srv not available

Added by okurz almost 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2020-12-07
Due date:
2021-02-24
% Done:

0%

Estimated time:

Description

Observation

In https://app.circleci.com/pipelines/github/os-autoinst/openQA/5211/workflows/9d31f5c4-fd61-410e-890d-0006dfef245f/jobs/49513/parallel-runs/0/steps/0-111?invite=true (raw document: https://circleci.com/api/v1.1/project/github/os-autoinst/openQA/49513/output/111/0?file=true&allocation-id=5fce507fd2bd8103886c1465-0-build%2F71C05C00) I saw t/full-stack.t failing with

RETRY=0 timeout -s SIGINT -k 5 -v $((9 * (0 + 1) ))m tools/retry prove -l --harness TAP::Harness::JUnit --timer t/full-stack.t
[16:26:38] t/full-stack.t .. 375/? # full result panel contents:
# State: scheduled
# Scheduled product: job has not been created by posting an ISO
# 50

#   Failed test 'test 1 is running'
#   at t/full-stack.t line 128.
Bailout called.  Further testing stopped:  URL for os-autoinst cmd srv not available

full log from background services available in https://app.circleci.com/pipelines/github/os-autoinst/openQA/5211/workflows/9d31f5c4-fd61-410e-890d-0006dfef245f/jobs/49513/artifacts

I think I have seen this in before.

Steps to reproduce

TBC

Expected result

t/full-stack.t should be stable, e.g. in 1000/1000 runs.

Suggestions


Related issues 1 (1 open0 closed)

Copied from openQA Project (public) - action #72085: flaky/unstable t/05-scheduler-full.t, Failed test 'Allocated maximum number of jobs that could have been allocated'Workable

Actions
Actions

Also available in: Atom PDF