action #21778
closed
4 seconds for 'all-conflicts-resolved-packages' is too short in update test
Added by mlin7442 over 6 years ago.
Updated over 6 years ago.
Category:
Bugs in existing tests
Description
Description
Observation
openQA test in opensuse-Tumbleweed-NET-x86_64-Build20170802-update_123@64bit fails in start_install,
also fails in NET-update_121 and NET-update_122, NOTE that it's random, but see that happened often recently.
Reproducible
Fails since (at least) Build 20170801
Expected result
Should not random fail.
Further details
The root cause should be 4 seconds for 'all-conflicts-resolved-packages' is too short, see https://openqa.opensuse.org/tests/461630#step/start_install/14
increase the timeout should help.
retry does help as it's random, but sooooo annoying.
- Category set to Bugs in existing tests
- Assignee set to Anonymous
- Priority changed from Normal to High
if it's "soooo annoying" then I guess it deserves a "high" prio :-)
yi, can you take a look please?
We can increase the time here as a quick solution. However I see a lot of code duplications here. I'll try to make the code clearer and shorter.
- Status changed from New to In Progress
Yes, that would be appreciated. I suggest you provide a fix in short term (i.e. today or monday, simply bump the timeout and verify that it works) and then clean up the code afterwards, preferably paired with not wasting time then with too high timeouts on check_screens when they won't match normally.
Oliver, my working directory is at NIS server, and I didn't get VPN working today. So today I won't be able to do a quick fix. :( Next week I'll be on vacation. Maybe someone else can do the quick fix today or next week, and then I'll clean up the code when I'm back from vacation.
- Assignee deleted (
Anonymous)
ok, good point. Thanks for noticing.
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
Also available in: Atom
PDF