Intermittent /IndexedDB/idb-explicit-commit.any.html | single tracking bug
Categories
(Core :: Storage: IndexedDB, defect, P2)
Tracking
()
People
(Reporter: intermittent-bug-filer, Assigned: janv)
References
(Regression)
Details
(Keywords: intermittent-failure, intermittent-testcase, regression)
Attachments
(6 files, 1 obsolete file)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review |
Filed by: ctuns [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=395715874&repo=mozilla-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/aNn7vy0LQheMc7t8BwJ38Q/runs/0/artifacts/public/logs/live_backing.log
[task 2022-11-06T23:11:00.637Z] 23:11:00 INFO - TEST-PASS | /IndexedDB/idb-explicit-commit.any.html | Calling abort on a committed transaction throws and does not prevent persisting the data.
[task 2022-11-06T23:11:00.637Z] 23:11:00 INFO - TEST-UNEXPECTED-TIMEOUT | /IndexedDB/idb-explicit-commit.any.html | Calling txn.commit() when txn is inactive should throw. - Test timed out
[task 2022-11-06T23:11:00.638Z] 23:11:00 INFO -
[task 2022-11-06T23:11:00.638Z] 23:11:00 INFO - TEST-UNEXPECTED-NOTRUN | /IndexedDB/idb-explicit-commit.any.html | Transactions with same scope should stay in program order, even if one calls commit. - expected PASS
[task 2022-11-06T23:11:00.639Z] 23:11:00 INFO -
[task 2022-11-06T23:11:00.639Z] 23:11:00 INFO - TEST-UNEXPECTED-NOTRUN | /IndexedDB/idb-explicit-commit.any.html | Transactions that explicitly commit and have errors should abort. - expected FAIL
[task 2022-11-06T23:11:00.640Z] 23:11:00 INFO - TEST-INFO | expected FAIL
[task 2022-11-06T23:11:00.641Z] 23:11:00 INFO -
[task 2022-11-06T23:11:00.641Z] 23:11:00 INFO - TEST-UNEXPECTED-NOTRUN | /IndexedDB/idb-explicit-commit.any.html | Transactions that handle all errors properly should behave as expected when an explicit commit is called in an onerror handler. - expected PASS
[task 2022-11-06T23:11:00.642Z] 23:11:00 INFO - TEST-UNEXPECTED-TIMEOUT | /IndexedDB/idb-explicit-commit.any.html | expected ERROR
[task 2022-11-06T23:11:00.643Z] 23:11:00 INFO - TEST-INFO expected ERROR | took 10126ms
[task 2022-11-06T23:11:00.645Z] 23:11:00 INFO - PID 6772 | 1667776260636 Marionette INFO Stopped listening on port 49902
[task 2022-11-06T23:11:01.616Z] 23:11:01 INFO - PID 6772 | WARNING: A blocker encountered an error while we were waiting.
[task 2022-11-06T23:11:01.618Z] 23:11:01 INFO - PID 6772 | Blocker: Waiting for ping task
[task 2022-11-06T23:11:01.618Z] 23:11:01 INFO - PID 6772 | Phase: TelemetryController: Waiting for pending ping activity
[task 2022-11-06T23:11:01.619Z] 23:11:01 INFO - PID 6772 | State: (none)
[task 2022-11-06T23:11:01.620Z] 23:11:01 INFO - PID 6772 | WARNING: Error: Phase "profile-before-change" is finished, it is too late to register completion condition "OS.File: flush I/O queued before profileBeforeChange"
[task 2022-11-06T23:11:01.621Z] 23:11:01 INFO - PID 6772 | WARNING: addBlocker@resource://gre/modules/AsyncShutdown.jsm:703:15
[task 2022-11-06T23:11:01.621Z] 23:11:01 INFO - PID 6772 | addBlocker@resource://gre/modules/AsyncShutdown.jsm:511:26
[task 2022-11-06T23:11:01.622Z] 23:11:01 INFO - PID 6772 | addBlocker@resource://gre/modules/AsyncShutdown.jsm:450:15
[task 2022-11-06T23:11:01.622Z] 23:11:01 INFO - PID 6772 | setupShutdown@resource://gre/modules/osfile/osfile_async_front.jsm:1563:28
[task 2022-11-06T23:11:01.623Z] 23:11:01 INFO - PID 6772 | @resource://gre/modules/osfile/osfile_async_front.jsm:1583:16
[task 2022-11-06T23:11:01.623Z] 23:11:01 INFO - PID 6772 | @resource://gre/modules/osfile.jsm:12:30
[task 2022-11-06T23:11:01.624Z] 23:11:01 INFO - PID 6772 | @resource://gre/modules/TelemetryStorage.jsm:19:28
[task 2022-11-06T23:11:01.624Z] 23:11:01 INFO - PID 6772 | promiseArchivePing@resource://gre/modules/TelemetryArchive.jsm:103:5
[task 2022-11-06T23:11:01.625Z] 23:11:01 INFO - PID 6772 | promiseArchivePing@resource://gre/modules/TelemetryArchive.jsm:63:33
[task 2022-11-06T23:11:01.625Z] 23:11:01 INFO - PID 6772 | _submitPingLogic@resource://gre/modules/TelemetryControllerParent.jsm:554:48
[task 2022-11-06T23:11:01.626Z] 23:11:01 INFO - PID 6772 | send@resource://gre/modules/TelemetryControllerParent.jsm:642:24
[task 2022-11-06T23:11:01.627Z] 23:11:01 INFO - PID 6772 | submitExternalPing@resource://gre/modules/TelemetryControllerParent.jsm:182:17
[task 2022-11-06T23:11:01.628Z] 23:11:01 INFO - PID 6772 | sendPing@resource://gre/modules/EventPing.jsm:51:30
[task 2022-11-06T23:11:01.628Z] 23:11:01 INFO - PID 6772 | _submitPing@resource://gre/modules/EventPing.jsm:229:12
[task 2022-11-06T23:11:01.629Z] 23:11:01 INFO - PID 6772 | shutdown@resource://gre/modules/EventPing.jsm:112:10
[task 2022-11-06T23:11:01.630Z] 23:11:01 INFO - PID 6772 | _cleanupOnShutdown@resource://gre/modules/TelemetryControllerParent.jsm:954:31
[task 2022-11-06T23:11:01.630Z] 23:11:01 INFO - PID 6772 | shutdown/<@resource://gre/modules/TelemetryControllerParent.jsm:1024:24
[task 2022-11-06T23:11:01.631Z] 23:11:01 INFO - PID 6772 | observe@resource://gre/modules/AsyncShutdown.jsm:560:16
[task 2022-11-06T23:11:01.637Z] 23:11:01 INFO - PID 6772 | WARNING: A blocker encountered an error while we were waiting.
[task 2022-11-06T23:11:01.638Z] 23:11:01 INFO - PID 6772 | Blocker: Waiting for ping task
[task 2022-11-06T23:11:01.638Z] 23:11:01 INFO - PID 6772 | Phase: TelemetryController: Waiting for pending ping activity
[task 2022-11-06T23:11:01.639Z] 23:11:01 INFO - PID 6772 | State: (none)
[task 2022-11-06T23:11:01.640Z] 23:11:01 INFO - PID 6772 | WARNING: Error: Phase "profile-before-change" is finished, it is too late to register completion condition "OS.File: flush I/O queued before profileBeforeChange"
[task 2022-11-06T23:11:01.640Z] 23:11:01 INFO - PID 6772 | WARNING: addBlocker@resource://gre/modules/AsyncShutdown.jsm:703:15
[task 2022-11-06T23:11:01.641Z] 23:11:01 INFO - PID 6772 | addBlocker@resource://gre/modules/AsyncShutdown.jsm:511:26
[task 2022-11-06T23:11:01.642Z] 23:11:01 INFO - PID 6772 | addBlocker@resource://gre/modules/AsyncShutdown.jsm:450:15
[task 2022-11-06T23:11:01.643Z] 23:11:01 INFO - PID 6772 | setupShutdown@resource://gre/modules/osfile/osfile_async_front.jsm:1563:28
[task 2022-11-06T23:11:01.644Z] 23:11:01 INFO - PID 6772 | @resource://gre/modules/osfile/osfile_async_front.jsm:1583:16
[task 2022-11-06T23:11:01.644Z] 23:11:01 INFO - PID 6772 | @resource://gre/modules/osfile.jsm:12:30
[task 2022-11-06T23:11:01.645Z] 23:11:01 INFO - PID 6772 | @resource://gre/modules/TelemetryStorage.jsm:19:28
[task 2022-11-06T23:11:01.645Z] 23:11:01 INFO - PID 6772 | promiseArchivePing@resource://gre/modules/TelemetryArchive.jsm:103:5
[task 2022-11-06T23:11:01.646Z] 23:11:01 INFO - PID 6772 | promiseArchivePing@resource://gre/modules/TelemetryArchive.jsm:63:33
[task 2022-11-06T23:11:01.646Z] 23:11:01 INFO - PID 6772 | _submitPingLogic@resource://gre/modules/TelemetryControllerParent.jsm:554:48
[task 2022-11-06T23:11:01.647Z] 23:11:01 INFO - PID 6772 | send@resource://gre/modules/TelemetryControllerParent.jsm:642:24
[task 2022-11-06T23:11:01.647Z] 23:11:01 INFO - PID 6772 | submitExternalPing@resource://gre/modules/TelemetryControllerParent.jsm:182:17
[task 2022-11-06T23:11:01.648Z] 23:11:01 INFO - PID 6772 | saveShutdownPings@resource://gre/modules/TelemetrySession.jsm:982:34
[task 2022-11-06T23:11:01.649Z] 23:11:01 INFO - PID 6772 | shutdownChromeProcess/cleanup/<@resource://gre/modules/TelemetrySession.jsm:1232:20
[task 2022-11-06T23:11:01.650Z] 23:11:01 INFO - PID 6772 | cleanup@resource://gre/modules/TelemetrySession.jsm:1239:9
[task 2022-11-06T23:11:01.651Z] 23:11:01 INFO - PID 6772 | shutdownChromeProcess@resource://gre/modules/TelemetrySession.jsm:1256:14
[task 2022-11-06T23:11:01.651Z] 23:11:01 INFO - PID 6772 | shutdown@resource://gre/modules/TelemetrySession.jsm:247:17
[task 2022-11-06T23:11:01.652Z] 23:11:01 INFO - PID 6772 | _cleanupOnShutdown@resource://gre/modules/TelemetryControllerParent.jsm:973:35
[task 2022-11-06T23:11:01.653Z] 23:11:01 INFO - PID 6772 | observe@resource://gre/modules/AsyncShutdown.jsm:560:16
[task 2022-11-06T23:11:01.653Z] 23:11:01 INFO - PID 6772 | WARNING: A blocker encountered an error while we were waiting.
[task 2022-11-06T23:11:01.653Z] 23:11:01 INFO - PID 6772 | Blocker: TelemetryController: shutting down
[task 2022-11-06T23:11:01.654Z] 23:11:01 INFO - PID 6772 | Phase: profile-before-change-telemetry
[task 2022-11-06T23:11:01.655Z] 23:11:01 INFO - PID 6772 | State: Error getting state: Error: Phase "profile-before-change" is finished, it is too late to register completion condition "OS.File: flush I/O queued before profileBeforeChange" at addBlocker@resource://gre/modules/AsyncShutdown.jsm:703:15
[task 2022-11-06T23:11:01.655Z] 23:11:01 INFO - PID 6772 | addBlocker@resource://gre/modules/AsyncShutdown.jsm:511:26
[task 2022-11-06T23:11:01.656Z] 23:11:01 INFO - PID 6772 | addBlocker@resource://gre/modules/AsyncShutdown.jsm:450:15
[task 2022-11-06T23:11:01.657Z] 23:11:01 INFO - PID 6772 | setupShutdown@resource://gre/modules/osfile/osfile_async_front.jsm:1563:28
[task 2022-11-06T23:11:01.657Z] 23:11:01 INFO - PID 6772 | @resource://gre/modules/osfile/osfile_async_front.jsm:1583:16
[task 2022-11-06T23:11:01.658Z] 23:11:01 INFO - PID 6772 | @resource://gre/modules/osfile.jsm:12:30
[task 2022-11-06T23:11:01.658Z] 23:11:01 INFO - PID 6772 | @resource://gre/modules/TelemetryStorage.jsm:19:28
[task 2022-11-06T23:11:01.659Z] 23:11:01 INFO - PID 6772 | getShutdownState@resource://gre/modules/TelemetrySend.jsm:1687:7
[task 2022-11-06T23:11:01.659Z] 23:11:01 INFO - PID 6772 | getShutdownState@resource://gre/modules/TelemetrySend.jsm:369:30
[task 2022-11-06T23:11:01.660Z] 23:11:01 INFO - PID 6772 | _getState@resource://gre/modules/TelemetryControllerParent.jsm:1072:38
[task 2022-11-06T23:11:01.660Z] 23:11:01 INFO - PID 6772 | setupTelemetry/<@resource://gre/modules/TelemetryControllerParent.jsm:931:18
[task 2022-11-06T23:11:01.661Z] 23:11:01 INFO - PID 6772 | safeGetState@resource://gre/modules/AsyncShutdown.jsm:242:17
[task 2022-11-06T23:11:01.661Z] 23:11:01 INFO - PID 6772 | Barrier/addBlocker/promise<@resource://gre/modules/AsyncShutdown.jsm:751:20
[task 2022-11-06T23:11:01.662Z] 23:11:01 INFO - PID 6772 | observe@resource://gre/modules/AsyncShutdown.jsm:560:16
[task 2022-11-06T23:11:01.663Z] 23:11:01 INFO - PID 6772 | WARNING: Error: Phase "profile-before-change" is finished, it is too late to register completion condition "OS.File: flush I/O queued before profileBeforeChange"
[task 2022-11-06T23:11:01.663Z] 23:11:01 INFO - PID 6772 | WARNING: addBlocker@resource://gre/modules/AsyncShutdown.jsm:703:15
[task 2022-11-06T23:11:01.664Z] 23:11:01 INFO - PID 6772 | addBlocker@resource://gre/modules/AsyncShutdown.jsm:511:26
[task 2022-11-06T23:11:01.665Z] 23:11:01 INFO - PID 6772 | addBlocker@resource://gre/modules/AsyncShutdown.jsm:450:15
[task 2022-11-06T23:11:01.665Z] 23:11:01 INFO - PID 6772 | setupShutdown@resource://gre/modules/osfile/osfile_async_front.jsm:1563:28
[task 2022-11-06T23:11:01.665Z] 23:11:01 INFO - PID 6772 | @resource://gre/modules/osfile/osfile_async_front.jsm:1583:16
[task 2022-11-06T23:11:01.666Z] 23:11:01 INFO - PID 6772 | @resource://gre/modules/osfile.jsm:12:30
[task 2022-11-06T23:11:01.667Z] 23:11:01 INFO - PID 6772 | @resource://gre/modules/TelemetryStorage.jsm:19:28
[task 2022-11-06T23:11:01.667Z] 23:11:01 INFO - PID 6772 | removeAbortedSessionPing@resource://gre/modules/TelemetryControllerParent.jsm:735:5
[task 2022-11-06T23:11:01.668Z] 23:11:01 INFO - PID 6772 | removeAbortedSessionPing@resource://gre/modules/TelemetryControllerParent.jsm:249:17
[task 2022-11-06T23:11:01.668Z] 23:11:01 INFO - PID 6772 | shutdownChromeProcess/cleanup/<@resource://gre/modules/TelemetrySession.jsm:1235:42
[task 2022-11-06T23:11:01.669Z] 23:11:01 INFO - PID 6772 | observe@resource://gre/modules/AsyncShutdown.jsm:560:16
[task 2022-11-06T23:11:01.729Z] 23:11:01 INFO - PID 6772 | JavaScript error: resource://gre/modules/AsyncShutdown.jsm, line 703: Error: Phase "profile-before-change" is finished, it is too late to register completion condition "OS.File: flush I/O queued before profileBeforeChange"
[task 2022-11-06T23:11:01.735Z] 23:11:01 INFO - PID 6772 | JavaScript error: resource://gre/modules/AsyncShutdown.jsm, line 703: Error: Phase "profile-before-change" is finished, it is too late to register completion condition "OS.File: flush I/O queued before profileBeforeChange"
[task 2022-11-06T23:11:01.736Z] 23:11:01 INFO - PID 6772 | JavaScript error: resource://gre/modules/AsyncShutdown.jsm, line 703: Error: Phase "profile-before-change" is finished, it is too late to register completion condition "OS.File: flush I/O queued before profileBeforeChange"
[task 2022-11-06T23:11:01.736Z] 23:11:01 INFO - PID 6772 | JavaScript error: resource://gre/modules/AsyncShutdown.jsm, line 703: Error: Phase "profile-before-change" is finished, it is too late to register completion condition "OS.File: flush I/O queued before profileBeforeChange"
[task 2022-11-06T23:11:01.737Z] 23:11:01 INFO - PID 6772 | JavaScript error: resource://gre/modules/AsyncShutdown.jsm, line 703: Error: Phase "profile-before-change" is finished, it is too late to register completion condition "OS.File: flush I/O queued before profileBeforeChange"
[task 2022-11-06T23:11:01.795Z] 23:11:01 INFO - Browser exited with return code 0
[task 2022-11-06T23:11:01.800Z] 23:11:01 INFO - Closing logging queue
[task 2022-11-06T23:11:01.801Z] 23:11:01 INFO - queue closed
[task 2022-11-06T23:11:01.870Z] 23:11:01 INFO - Application command: Z:\task_166777286560419\build\application\firefox\firefox.exe -marionette about:blank --wait-for-browser -profile C:\Users\task_166777286560419\AppData\Local\Temp\tmpbnuk82em
[task 2022-11-06T23:11:01.879Z] 23:11:01 INFO - PID 3884 | 1667776145944 Marionette INFO Marionette enabled
[task 2022-11-06T23:11:01.880Z] 23:11:01 INFO - PID 3884 | 1667776145948 Marionette INFO Listening on port 49903
[task 2022-11-06T23:11:01.881Z] 23:11:01 INFO - PID 3884 | console.warn: SearchSettings: "get: No settings file exists, new profile?" (new NotFoundError("Could not open the file at C:\\Users\\task_166777286560419\\AppData\\Local\\Temp\\tmpkvt6ahmp\\search.json.mozlz4", (void 0)))
[task 2022-11-06T23:11:01.882Z] 23:11:01 INFO - PID 3884 | *** You are running in background task mode. ***
[task 2022-11-06T23:11:01.883Z] 23:11:01 INFO - PID 3884 | *** You are running in headless mode.
[task 2022-11-06T23:11:01.884Z] 23:11:01 INFO - PID 3884 | console.error: "C:\\Users\\task_166777286560419\\AppData\\Local\\Temp\\tmpkvt6ahmp" "" 0 ".purge.bg_rm"
[task 2022-11-06T23:11:01.884Z] 23:11:01 INFO - Starting runner
[task 2022-11-06T23:11:02.919Z] 23:11:02 INFO - TEST-START | /IndexedDB/idb-explicit-commit.any.worker.html
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 31•2 years ago
|
||
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.
| Reporter | ||
Comment 32•2 years ago
|
||
| treeherder | ||
New failure instance: https://treeherder.mozilla.org/logviewer?job_id=422962497&repo=mozilla-central
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 35•2 years ago
|
||
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.
| Reporter | ||
Comment 36•2 years ago
|
||
| treeherder | ||
New failure instance: https://treeherder.mozilla.org/logviewer?job_id=426828338&repo=autoland
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 41•2 years ago
|
||
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.
| Reporter | ||
Comment 42•2 years ago
|
||
| treeherder | ||
New failure instance: https://treeherder.mozilla.org/logviewer?job_id=432025186&repo=autoland
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 47•2 years ago
|
||
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.
| Reporter | ||
Comment 48•2 years ago
|
||
| treeherder | ||
New failure instance: https://treeherder.mozilla.org/logviewer?job_id=440092248&repo=autoland
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 52•2 years ago
|
||
Frequency might have started to increase around here: range
Olli, any chance you could check this out?
Thank you!
| Comment hidden (Intermittent Failures Robot) |
Comment 54•2 years ago
|
||
That hints that this is a real issue somewhere in IDB code. Something there relies on particular GC/CC behavior.
Updated•2 years ago
|
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 57•2 years ago
|
||
Update
There have been 55 total failures within the last 7 days:
- 7 failures on Linux 18.04 WebRender Shippable op
- 48 failures on Linux 18.04 x64 WebRender debug
Recent log: https://treeherder.mozilla.org/logviewer?job_id=442070823&repo=mozilla-central&lineNumber=2523
Comment 58•2 years ago
|
||
In the logs for debug builds on CI I see often NS_ERROR_STORAGE_BUSY errors coming from quotamanager.
And the subtest "Transactions that explicitly commit and have errors should abort." which seems to fail now often was already marked to intermittently fail in quite a few cases even before the GC scheduling change
https://searchfox.org/mozilla-central/rev/5f17a6bd35bcce02371973db89bf0196e83b93b6/testing/web-platform/meta/IndexedDB/idb-explicit-commit.any.js.ini#12-20
And based on the .ini file, also other subtests have issues.
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Updated•1 year ago
|
We're also failing this test on the interop2024 WPT harness.
| Comment hidden (Intermittent Failures Robot) |
| Assignee | ||
Comment 64•1 year ago
|
||
I ran the test locally in the verify mode, but it passed successfully.
Forwarding the needinfo to Jari since he is now focusing on interop-2024-indexeddb bugs.
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 66•1 year ago
|
||
This is interesting, bug 1609957 fixed a race condition, but it introduced a dependency on another race. This time, it's a problem with request serial numbers not being in sync between the parent and child. The serial numbers were used only for logging before, now they are also used for explicit commit which is probably not a good idea.
What is even worse, bug 934640 somehow increases the frequency of this intermittent failure, blocking landing of patches for bug 934640.
Now when we know that there's a new race, it's probably not surprising that changes which are not directly related (bug 934640) may affect the frequency of the intermittent failure. It was already mentioned that a small change in GC/CC behavior affects this intermittent failure as well.
I have a WIP patch to fix this and initial testing on try confirms that exact tracking of request/operation ids fixes this intermittent failure.
https://treeherder.mozilla.org/jobs?repo=try&revision=5de97e3b1db8127490a7340f2f2e88aded924e3d
Comment 67•1 year ago
|
||
Set release status flags based on info from the regressing bug 1609957
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 68•1 year ago
|
||
This patch adds only new member variables, actual support for sending ids will
be added in individual patches (all operations have zero id for now). The idea
is to have only one source of truth, so id used in the parent actor and child
actor is always the same.
Updated•1 year ago
|
| Assignee | ||
Comment 69•1 year ago
|
||
| Assignee | ||
Comment 70•1 year ago
|
||
| Assignee | ||
Comment 71•1 year ago
|
||
| Assignee | ||
Comment 72•1 year ago
|
||
Explicitly committed transactions are aborted in case of a failed request that
was started after committing was initiated. The order of requests is currently
tracked by storing request serial numbers. However, request serial numbers are
not always in sync between parent and child, so they are only suitable for
logging purposes. This patch switches from request serial numbers to request
ids which are only generated by the child side and thus always in sync between
parent and child.
| Assignee | ||
Comment 73•1 year ago
|
||
Comment 74•1 year ago
|
||
Set release status flags based on info from the regressing bug 1609957
| Assignee | ||
Updated•1 year ago
|
Comment 75•1 year ago
|
||
Comment 76•1 year ago
|
||
| bugherder | ||
Comment 77•1 year ago
|
||
| Assignee | ||
Updated•1 year ago
|
Comment 78•1 year ago
|
||
Comment 79•1 year ago
|
||
| bugherder | ||
Comment 80•1 year ago
|
||
Backed out for causing wpt failures in idlharness.https.html.
- Backout link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-PASS | /html/dom/idlharness.https.html?exclude=(Document|Window|HTML.*) | ElementInternals interface: attribute states - expected FAIL
Comment 81•1 year ago
|
||
Comment 82•1 year ago
|
||
Comment on attachment 9390490 [details]
Bug 1799374 - Require IndexedDB/idb-explicit-commit.any.html to always pass; r=#dom-storage
Revision D204214 was moved to bug 1887550. Setting attachment 9390490 [details] to obsolete.
Comment 84•1 year ago
|
||
Relanded https://hg.mozilla.org/integration/autoland/rev/730e6cc60956749bc49db3c7b2990781c6c40566 as another changeset was the culprit for the failures in Comment 80. Sorry for the confusion!
Updated•1 year ago
|
Comment 86•1 year ago
|
||
| bugherder | ||
| Comment hidden (Intermittent Failures Robot) |
Comment 88•1 year ago
|
||
The patch landed in nightly and beta is affected.
:janv, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox125towontfix.
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 89•1 year ago
|
||
The fix is not trivial, it would be better to let it ride the trains normally (instead of uplifting to beta).
Updated•1 year ago
|
| Comment hidden (Intermittent Failures Robot) |
Description
•