Project

General

Profile

Actions
Copy link

action #59879

open

module status "running" seems to report in very late or not at all

Added by okurz about 5 years ago. Updated almost 5 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
QA (public) - future
Start date:
2019-11-15
Due date:
% Done:

0%

Estimated time:

Description

Observation

See Screenshot_20191115_081243_no_running_module.png

there is no blue module status "running". As soon as the module entered the post_fail_hook it seems the "running" status appeared but it should have appeared way sooner.

Problem

I could reproduce this problem in http://lord.arch.suse.de/tests/2668 running a current os-autoinst. Reverting to os-autoinst a7874588 before 87276ac7 which I suspected might be related seems to behave better. A status "running" shows up immediately after the job went to status "running".

Files

Screenshot_20191115_081243_no_running_module.png (33.1 KB) Screenshot_20191115_081243_no_running_module.png okurz, 2019-11-15 09:55
Actions
Copy link
 #1

Updated by okurz almost 5 years ago

  • Category changed from Regressions/Crashes to Feature requests
  • Priority changed from Normal to Low
  • Target version set to future

working "as designed", maybe not really a regression.

Actions
Copy link

Also available in: Atom PDF