[opensuse][functional]sporadic][u] chromium test is unstable
https://openqa.opensuse.org/tests/677588#step/chromium/17 accepts incomplete chromium startup (slow loading of home page) and then types about: blindly - resulting in a good for 'out:'
pop up dialog about translation breaks needle match, suggest to workaround this issue.
low performance issue sometimes should be handled as well, suggest to increase timeout for needle match.
link to latest
#3 Updated by okurz about 4 years ago
- Subject changed from [opensuse] chromium test is unstable to [opensuse][functional][u][fast] chromium test is unstable
- Due date set to 2018-07-03
- Category changed from Enhancement to existing tests to Bugs in existing tests
- Status changed from New to In Progress
- Assignee set to okurz
- Target version set to Milestone 17
#4 Updated by okurz about 4 years ago
- Status changed from In Progress to Feedback
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5280 merged. I should recheck at EOS if there are further chromium-related unstabilities.
#6 Updated by okurz about 4 years ago
- Status changed from Feedback to Blocked
Checked the linked scenario from latest and back from there, around 30/30 jobs did not fail in chromium: https://openqa.opensuse.org/tests/697882
https://openqa.opensuse.org/tests/697619#step/chromium/19 is the latest "chromium" test failure on current openSUSE Tumbleweed.
I am wondering about remaining "random chromium failures" in openQA tests, e.g. https://openqa.opensuse.org/tests/697619#step/chromium/19 shows that the test fails to type in the adress bar however the journal states a core dump about snapper. That sounds related to system is slowed down and chromium is just slow to react. We should not work around this in tests but detect the errors and report these, at best automatically from tests. I wonder if we can turn a fail into a soft-fail from a post_fail_hook, hm…
For now test labeled with https://bugzilla.suse.com/show_bug.cgi?id=1079877
I guess also here it would make sense to solve #31351 first to ensure that the maintenance tasks have been completed in the background.
#24 Updated by zluo almost 4 years ago
atm update tests are not stable and got failed sometimes:
#26 Updated by zluo almost 4 years ago
- Subject changed from [opensuse][functional][u] chromium test is unstable to [opensuse][functional]sporadic][u] chromium test is unstable
started over 50 test runs and 99% are just passed. but I can still see failed test run like:
it shows html test failed because the page is not loaded at all. It could be a network issue or performance issue. I need more test runs...
Anyway this becomes sporadic issue, the initial issue with translate dialog is gone.
#27 Updated by zluo almost 4 years ago
http://e13.suse.de/tests/8106#step/zypper_add_repos/16 shows problem with zypper_add_repos:
can't find a valid repository at given location
#30 Updated by zluo almost 4 years ago
- Status changed from In Progress to Resolved