QA » openQA Project » openQA Tests

On investigation, this failure is for the needle yast2-ask-reboot not matched on SLE15. We need clone the job to local and modify code to save the screen to create the needle on local, then submit MR to fix it.

MR submitted.

https://gitlab.suse.de/openqa/os-autoinst-needles-sles/merge_requests/1002

I've experience similar issue, but even worse, as we have timeout on the pop-up I tried to catch. As of now there is no better way than changing code =(

So the developer mode wasn't helpful here?

Yes, on developer mode I can't create new needle now, I think the create needle should be support on developer mode.

Hi Oliver, this job failed just for the expected needle not matched, it is no relationship with the MAX_JOB_TIME, in fact the default max job time(2h) is enough for this case. We will set enough MAX_JOB_TIME if needed.

sure, I understand why the job failed. The problem with incomplete jobs is that they are hard to review because a label carry over does not work. This is why I suggest to ensure that a high enough MAX_JOB_TIME is used in all test suites

And with https://github.com/os-autoinst/openQA/pull/1855/files#diff-454b55e3d1e6f1147a46142480c71a85R1251 temporarily adjusting code on production is also even easier :)

Status changed from In Progress to Workable
% Done changed from 100 to 0

Comment Edit

@leli

Yes, on developer mode I can't create new needle now

You can put an assert_screen for a non-existent needle in your code. The developer mode allows to pause here (instead of failing) and automatically makes a screenshot to create a new needle from. You can repeat that multiple times in one testrun. Of course you need to adjust the test code manually to add the new assert_screens but the developer mode should still improve the workflow (you don't need to add code to create screenshots).

I think the create needle should be support on developer mode.

What is missing in the developer mode?
@mkittler, in fact, I can clone job and modify code locally to create needle, while this is a bit inconvenient since need submit MR to merge it. If we can add create new needle function on developer mode it will be very helpful for us. Thanks.

@okurz, I understand your meaning, while for this incomplete case, increase MAX_JOB_TIME won't help since it will stall there until time out. Thanks for the document for 'temporarily adjusting code ', its very helpful.:)

leli wrote:

@okurz, I understand your meaning, while for this incomplete case, increase MAX_JOB_TIME won't help since it will stall there until time out.

Well, then this is what should be prevented as well then :)