Frequent TSAN mozilla/tests/webdriver/execute_async_script/execute_async.py | test_no_abort_by_user_prompt_in_other_tab[alert] - webdriver.error.NoSuchAlertException: no such alert (404):
Categories
(Remote Protocol :: Marionette, defect, P1)
Tracking
(firefox110 disabled, firefox116 disabled, firefox117 disabled, firefox118 fixed)
People
(Reporter: intermittent-bug-filer, Assigned: whimboo)
References
(Blocks 2 open bugs)
Details
(Keywords: intermittent-failure)
Attachments
(1 file, 1 obsolete file)
Filed by: rvandermeulen [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=400434061&repo=try
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/cuHEonnBSDOEIysCVAJMuw/runs/0/artifacts/public/logs/live_backing.log
This hits about 60% of the time when running wdspec in TSAN mode.
| Comment hidden (Intermittent Failures Robot) |
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 2•2 years ago
|
||
Ryan, I cannot see any other failure since your original report. I would tend to close this bug as incomplete if you don't mind.
Comment 3•2 years ago
|
||
We annotated the failures in the patch that enabled the suite.
https://hg.mozilla.org/mozilla-central/diff/655ea8a131bf1230e0b9b50cb6e5a5c9d9f2025a/testing/web-platform/mozilla/meta/webdriver/execute_async_script/execute_async.py.ini
| Assignee | ||
Comment 4•2 years ago
|
||
Ah gotcha. I forgot that. As best lets mark the test as disabled (no better keyword available) to easily see that we have multiple states set.
Comment 5•2 years ago
|
||
| Assignee | ||
Comment 6•2 years ago
|
||
This failure seems to be fixed. At least there was no failure when I pushed to try with the patches attached to bug 1847578. We are going to re-enable.
| Assignee | ||
Comment 7•2 years ago
|
||
Lets see if we can get this test enabled as well given that nearly ever other test got enabled as well via bug 1847578. That one and the one from bug 1789355 I actually missed as it looks like.
| Assignee | ||
Comment 8•2 years ago
|
||
Actually there is no TSAN specific exception anymore in the test manifest. As such we do not have to keep this bug open anytime longer. The failures on Android are still present and have to be taken care of in bug 1789355.
| Assignee | ||
Comment 9•2 years ago
|
||
Actually these tests are still failing on Android and as such the metadata entry needs slightly to be updated. I'm going to upload a patch which will remove the multiple status for TSAN only.
| Assignee | ||
Comment 10•2 years ago
|
||
Comment 11•2 years ago
|
||
Comment 12•2 years ago
|
||
| bugherder | ||
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 13•2 years ago
|
||
This failure is actually not fixed and already failed 15 times since the patch got landed. Interesting that this didn't happen in the try builds. Here the relevant log:
I assume that this might be a race and that there is a delay for opening the prompt, which we do not encounter for at the moment.
Given the amount of failures I'll request a backout.
Comment 14•2 years ago
|
||
Backed out given the amount of failures.
Comment 15•2 years ago
|
||
Backout merged to central: https://hg.mozilla.org/mozilla-central/rev/885704eb2b54
| Assignee | ||
Comment 16•2 years ago
|
||
I'm going to leave this disabled for now until the test failure on bug 1789355 has been addressed. Maybe that will also fix the problem with TSAN builds.
Updated•2 years ago
|
| Comment hidden (Intermittent Failures Robot) |
| Assignee | ||
Comment 18•2 years ago
|
||
| Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 19•2 years ago
|
||
Comment 20•2 years ago
|
||
| bugherder | ||
| Assignee | ||
Updated•2 years ago
|
Description
•