QA » openQA Project

This is most likely because the worker didn't yet see that there is something running at all. Unusual problem :)

My non-expert investigation leans to conclusion that it is "by design": - start_time is updated when first message is received from worker. And "update status" messages are coming every 10 seconds as defined here https://github.com/os-autoinst/openQA/blob/64ccc82ec49796560ac09d5efa3fe8105a1655fc/lib/OpenQA/Worker/Common.pm#L66

So the quickest/simplest solution may be to somehow send simple message to the WebService "immediately" after job start.

But I would prefer solution when Worker is sending own explicit start and finish times to WebService. E.g it may do it in first/last message or explicit message packets. WebService may collect own timestamp version of 'first/last' messages received, which may be usable e.g. to understand eventual latency.

How can this be reproduced?
How can I create a job that takes less than 10s?

And which part is not displayed in the ui?

hi,

create a non sense test like https://github.com/cfconrad/os-autoinst-distri-opensuse/blob/sandbox_clemix/tests/clemix/nop.pm

And trigger just this, you will get a result like: http://cfconrad-vm.qa.suse.de/tests/5993
When waiting these 10 seconds before, you get: http://cfconrad-vm.qa.suse.de/tests/5994

cfconrad wrote:

create a non sense test like https://github.com/cfconrad/os-autoinst-distri-opensuse/blob/sandbox_clemix/tests/clemix/nop.pm

Ah, I see, i thought I always have to run the "boot_to_desktop" test first, that's why my test took longer in total.

I was able to reproduce it now with your test, thanks!

Like Andrii said, the first status call to isotovideo happens too late, so it doesn't get a response anymore.
As discussed with Sebastian, I am working on a replacement of the status call via socket. Instead it is using a status file that survives the end of isotovideo.

I created two draft pull requests:
https://github.com/os-autoinst/openQA/pull/2327
https://github.com/os-autoinst/os-autoinst/pull/1212

FYI, this ticket (bug) is blocking https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8329

Current Status:

I created the PRs which fixed the issue by using a status file.
However, one of the tests (t/33-developer_mode.t) was failing sometimes.
The status call we were using before had some side effect (which seems to be a timing thing only, but not sure).

I have now spent a long time debugging this (and learning to know a lot of our code during this), but the reason is still unclear.
We can't merge my PR until this is fixed.

We don't have a plan yet what to do about it.

The bug I mentioned is very probably fixed (PR https://github.com/os-autoinst/os-autoinst/pull/1230 still in review).
Then I can rebase my PRs for this issue.

Isn't this actually Low priority? On the other hand gh#os-autoinst/os-autoinst-distri-opensuse#8329 seems to be blocked by it.

We're on it. Sorry, it was blocked very long by a bug in os-autoinst that needed to be fixed first.
Second, it introduces a new way of communication between the openQA worker and isotovideo, so both repos were updated and we couldn't merge the second PR before the first was merged.

Second PR is in review and should be merged soon. https://github.com/os-autoinst/openQA/pull/2327

@tinita: thanks a lot for working on it :)

PR https://github.com/os-autoinst/openQA/pull/2327 was merged

cfconrad it was deployed to https://openqa.opensuse.org/, can you test?

hi @tinita, I run it in my own instance with latest openqa installed.
Looks good, nice!
http://cfconrad-vm.qa.suse.de/tests/6136
EDIT
http://cfconrad-vm.qa.suse.de/tests/6141 <= real test run

Regarding your hint, I took a look to the details page during run. And I had the attached intermediate state.
Don't know if this is something which should be covered as well.

Do you need some test run on openqa as well?

@cfconrad That in the intermediate state the short tests don't show is an additional issue. During working on this issue I couldn't figure out why it's happening.
Could you open a new issue for that? Thanks!

https://progress.opensuse.org/issues/58826 have fun with it :)