Project

General

Profile

action #113318

openQA live view stays blank when browser tab is staying open on scheduled jobs until jobs start size:M

Added by okurz about 1 month ago. Updated 18 days ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Category:
Concrete Bugs
Target version:
Start date:
2022-07-06
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

On any job (at least observed on openqa.opensuse.org) when opening the job while the job is still in scheduled state, when the job switches to "running" the live view stays blank (white rectangle with no content) like this:

Screenshot_20220706_145940_openQA_running_job_stays_white_when_staying_open_since_scheduled.png

Expected result

Live view should show actual content like this from the beginning:

Screenshot_20220706_150136_openQA_live_view_showing_content_expected_result.png

Workaround

Two alternatives:

  • Force a refresh of the browser window with "F5"
  • Open the job result only after the job started

Suggestions

  • Check whether works before https://github.com/os-autoinst/openQA/pull/4727
  • Tina/Marius observed a live view not updating an already running job, which might relate to this issue (also on o3)
  • Try to reproduce it locally
  • Investigate the worker's pool directory while the job is running

History

#1 Updated by cdywan about 1 month ago

  • Subject changed from openQA live view stays blank when browser tab is staying open on scheduled jobs until jobs start to openQA live view stays blank when browser tab is staying open on scheduled jobs until jobs start size:M
  • Description updated (diff)
  • Status changed from New to Workable

#2 Updated by tinita about 1 month ago

Just for the record, I don't see the problem locally or on osd, only on o3.
Can't see anything suspicious in the developer tools console / network log.

#3 Updated by mkittler about 1 month ago

  • Assignee set to mkittler

#4 Updated by mkittler about 1 month ago

I cannot reproduce the problem Tina and me saw on o3 with any running job on o3. Note that this problem was also happening with currently running jobs, e.g. Tina sent me the link and the updates also got stuck when I opened the running job on my machine. Currently o3 isn't busy at all.

The workaround "Open the job result only after the job started" implies that there's another case when it is only broken if the job wasn't running when opening the tab. I could also not reproduce that case. Neither on o3 nor locally. Note that it can take a while until the test actually gets started. So a test still shows up as running when the worker downloads assets, isotovideo is launched, needles are initialized and the test schedule is created. That can take a while. Maybe it was just that and the reload was just done shortly before the test was actually starting so it only looked like it helped?

The workaround "Force a refresh of the browser window with "F5"" implies that refreshing would help. That wasn't really the case on the job Tina and me observed. It helped but shortly the job got stuck again.

I'll check again next week when o3 is more busy. Maybe that makes a difference. Once I find a job I'll investigate the workers pool directory and logs.


I've also found a job where the video was disabled (due to max. job time). In this case one also doesn't get a screen. I suppose that was not the case here. I'm just mentioning it because at a first look such a job looks like it would reproduce some of the mentioned issues.

#5 Updated by mkittler about 1 month ago

Anybody, feel free to grab this ticket if you can reproduce it. I've opened a few tabs but so far haven't reproduced it.

#6 Updated by okurz about 1 month ago

I could still reproduce it as of today. Do you think it has something to do with my local environment, e.g. Firefox on Leap 15.3 x86_64 or something?

#7 Updated by mkittler 29 days ago

I don't think it is the Firefox version. Since this is about the image and likely also the log I don't think the relevant code requires any too new JavaScript features your possibly outdated browser doesn't have.

If you can reproduce it locally, you could open the developer tools in the tab and check whether anything shows up in the JavaScript console and network log when the job state switches to running.

#8 Updated by okurz 18 days ago

  • Assignee deleted (mkittler)
  • Target version changed from Ready to future

We have to focus on other urgent tasks with reduced capacity so moving this out of backlog

Also available in: Atom PDF