action #36304
closed[opensuse][functional]sporadic][u] chromium test is unstable
Added by coolo almost 6 years ago. Updated over 5 years ago.
0%
Description
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.
Further details¶
link to latest
Updated by JERiveraMoya almost 6 years ago
- Related to coordination #35302: [qe-core][opensuse][functional][epic][sporadic] Various unstable tests on o3 added
Updated by JERiveraMoya almost 6 years ago
- Subject changed from [opensuse] chromium test is unsable to [opensuse] chromium test is unstable
Updated by okurz almost 6 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
Updated by okurz almost 6 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.
Updated by okurz almost 6 years ago
- Related to action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally) added
Updated by okurz almost 6 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.
Updated by mgriessmeier almost 6 years ago
- Due date changed from 2018-07-03 to 2018-07-17
Updated by okurz almost 6 years ago
- Due date changed from 2018-07-17 to 2018-07-31
- Status changed from Blocked to Feedback
- Target version changed from Milestone 17 to Milestone 18
Seems we covered this now properly with #35685 -> cromium stable but I will monitor
Updated by okurz almost 6 years ago
Could not reproduce any problems locally but maybe we have some on production still …
Updated by okurz almost 6 years ago
- Copied to action #38702: [functional][u] apply workaround for bsc#1096401 "snapper terminates with core dump" added
Updated by okurz almost 6 years ago
- Copied to deleted (action #38702: [functional][u] apply workaround for bsc#1096401 "snapper terminates with core dump")
Updated by okurz almost 6 years ago
- Blocked by action #38702: [functional][u] apply workaround for bsc#1096401 "snapper terminates with core dump" added
Updated by okurz almost 6 years ago
- Description updated (diff)
- Due date changed from 2018-07-31 to 2018-08-14
We had an update in html5test.opensuse.org which is also causing fails in chromium. I guess it's better to revisit this with better statistics in the next sprint.
Updated by okurz over 5 years ago
- Status changed from Feedback to Workable
- Assignee deleted (
okurz)
stability of chromium test can be re-evaluated now
Updated by okurz over 5 years ago
- Due date changed from 2018-08-14 to 2018-08-28
bulk move to next sprint as could not be discussed in SR
Updated by okurz over 5 years ago
- Due date changed from 2018-08-28 to 2018-09-25
- Target version changed from Milestone 18 to Milestone 19
Updated by okurz over 5 years ago
- Subject changed from [opensuse][functional][u][fast] chromium test is unstable to [opensuse][functional][u] chromium test is unstable
Updated by zluo over 5 years ago
- Subject changed from [opensuse][functional][u] chromium test is unstable to [opensuse][functional][u] chromium test i
- Estimated time set to 2.00 h
Updated by mgriessmeier over 5 years ago
- Subject changed from [opensuse][functional][u] chromium test i to [opensuse][functional][u] chromium test is unstable
Updated by zluo over 5 years ago
- Status changed from Workable to In Progress
- Assignee set to zluo
take over
Updated by zluo over 5 years ago
atm update tests are not stable and got failed sometimes:
http://e13.suse.de/tests/8020#step/check_system_is_updated/9
Updated by zluo over 5 years ago
fixed one needle issue however:
http://e13.suse.de/tests/8021#step/chromium/17
failed for needle match of html tests:
http://e13.suse.de/tests/8021#step/chromium/21
Updated by zluo over 5 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:
http://e13.suse.de/tests/8063#
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.
Updated by zluo over 5 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
Updated by zluo over 5 years ago
http://e13.suse.de/tests/8463#next_previous
shows very stable test results.
Updated by zluo over 5 years ago
Updated by zluo over 5 years ago
- Status changed from In Progress to Resolved
Updated by okurz about 4 years ago
- Related to action #63334: [functional][u][sporadic] test fails in chromium to go to "about/version" page in adress bar added