Closed Bug 1852976 Opened 2 years ago Closed 1 month ago

Intermittent /fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.html | single tracking bug

Categories

(Core :: DOM: File, defect, P5)

defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr102 --- unaffected
firefox-esr115 --- unaffected
firefox117 --- unaffected
firefox118 --- unaffected
firefox119 --- affected
firefox120 --- affected

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Regression)

Details

(4 keywords)

Filed by: imoraru [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=428976140&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/bbUMquaoQHSohuJyRt-88g/runs/0/artifacts/public/logs/live_backing.log
Reftest URL: https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/bbUMquaoQHSohuJyRt-88g/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1


[task 2023-09-13T12:35:47.451Z] 12:35:47     INFO - TEST-START | /fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.html
[task 2023-09-13T12:35:47.514Z] 12:35:47     INFO - Setting pref dom.fs.enabled to true
[task 2023-09-13T12:35:47.534Z] 12:35:47     INFO - Setting pref dom.fs.writable_file_stream.enabled to true
[task 2023-09-13T12:35:48.392Z] 12:35:48     INFO - PID 2952 | ### XPCOM_MEM_BLOAT_LOG defined -- logging bloat/leaks to C:\Users\task_169460627911147\AppData\Local\Temp\tmp_ov4s_3f\runtests_leaks_2112_tab_pid9088.log
[task 2023-09-13T12:35:48.408Z] 12:35:48     INFO - PID 2952 | ### XPCOM_MEM_BLOAT_LOG defined -- logging bloat/leaks to C:\Users\task_169460627911147\AppData\Local\Temp\tmp_ov4s_3f\runtests_leaks_2112_tab_pid5436.log
[task 2023-09-13T12:35:50.935Z] 12:35:50     INFO - PID 2952 | [Parent 6584, StreamTrans #4] WARNING: QM_TRY failure (ERROR): 'mDataManager->MutableDatabaseManagerPtr()->RemoveFile(aRequest.handle()) failed with resultCode 0x80530007, resultName NS_ERROR_DOM_NO_MODIFICATION_ALLOWED_ERR, frameId 1, stackId 31, processId 6584', file dom/fs/parent/FileSystemManagerParent.cpp:405
[task 2023-09-13T12:35:50.942Z] 12:35:50     INFO - PID 2952 | [Parent 6584, StreamTrans #2] WARNING: QM_TRY failure (ERROR): 'mDataManager->MutableDatabaseManagerPtr()->RemoveFile(aRequest.handle()) failed with resultCode 0x80530007, resultName NS_ERROR_DOM_NO_MODIFICATION_ALLOWED_ERR, frameId 1, stackId 32, processId 6584', file dom/fs/parent/FileSystemManagerParent.cpp:405
[task 2023-09-13T12:35:50.945Z] 12:35:50     INFO - PID 2952 | [Parent 6584, StreamTrans #1] WARNING: QM_TRY failure (ERROR): 'mDataManager->MutableDatabaseManagerPtr()->RemoveFile(aRequest.handle()) failed with resultCode 0x80530007, resultName NS_ERROR_DOM_NO_MODIFICATION_ALLOWED_ERR, frameId 1, stackId 33, processId 6584', file dom/fs/parent/FileSystemManagerParent.cpp:405
[task 2023-09-13T12:35:50.972Z] 12:35:50     INFO - ..
[task 2023-09-13T12:35:50.972Z] 12:35:50     INFO - TEST-PASS | /fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.html | A writable stream in siloed mode takes a lock that is shared 
[task 2023-09-13T12:35:50.972Z] 12:35:50     INFO - TEST-PASS | /fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.html | When there's an open writable stream in siloed mode on a file, can open another writable stream in siloed on a different file 
[task 2023-09-13T12:35:50.981Z] 12:35:50     INFO - TEST-PASS | /fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.html | When there's an open writable stream in siloed mode on a file, can open another writable stream in exclusive on a different file 
[task 2023-09-13T12:35:50.981Z] 12:35:50     INFO - TEST-FAIL | /fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.html | When there's an open writable stream in siloed mode on a file, cannot open another writable stream in exclusive on that same file - assert_unreached: Should have rejected: undefined Reached unreachable code
[task 2023-09-13T12:35:50.981Z] 12:35:50     INFO - TEST-FAIL | /fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.html | After all writable streams in siloed mode on a file has been closed, can open another writable stream in exclusive on the same file - assert_unreached: Should have rejected: undefined Reached unreachable code
[task 2023-09-13T12:35:50.981Z] 12:35:50     INFO - TEST-FAIL | /fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.html | A writable stream in exclusive mode has a mode property equal to exclusive - assert_equals: expected (string) "exclusive" but got (undefined) undefined
[task 2023-09-13T12:35:50.981Z] 12:35:50     INFO - lockPropertyTests/<@https://web-platform.test:8443/fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.js:16:18
[task 2023-09-13T12:35:50.981Z] 12:35:50     INFO - TEST-FAIL | /fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.html | A writable stream in exclusive mode takes a lock that is exclusive - assert_equals: expected "exclusive" but got "shared"
[task 2023-09-13T12:35:50.981Z] 12:35:50     INFO - lockPropertyTests/<@https://web-platform.test:8443/fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.js:22:18
[task 2023-09-13T12:35:50.981Z] 12:35:50     INFO - TEST-PASS | /fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.html | When there's an open writable stream in exclusive mode on a file, can open another writable stream in siloed on a different file 
[task 2023-09-13T12:35:50.981Z] 12:35:50     INFO - TEST-FAIL | /fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.html | When there's an open writable stream in exclusive mode on a file, cannot open another writable stream in siloed on that same file - assert_unreached: Should have rejected: undefined Reached unreachable code
[task 2023-09-13T12:35:50.981Z] 12:35:50     INFO - TEST-FAIL | /fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.html | After a writable stream in exclusive mode on a file has been closed, can open another writable stream in siloed on the same file - assert_unreached: Should have rejected: undefined Reached unreachable code
[task 2023-09-13T12:35:50.982Z] 12:35:50     INFO - TEST-UNEXPECTED-FAIL | /fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.html | When there's an open writable stream in exclusive mode on a file, can open another writable stream in exclusive on a different file - promise_test: Unhandled rejection with value: object "NoModificationAllowedError: No modification allowed"
[task 2023-09-13T12:35:50.983Z] 12:35:50     INFO - ..
[task 2023-09-13T12:35:50.983Z] 12:35:50     INFO - TEST-OK | /fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.html | took 3521ms
[task 2023-09-13T12:35:50.983Z] 12:35:50     INFO - No more tests
[task 2023-09-13T12:35:50.986Z] 12:35:50     INFO - PID 2952 | 1694608550983	Marionette	INFO	Stopped listening on port 52387
Flags: needinfo?(aborovova)
Summary: Intermittent TV /fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.html | single tracking bug → Intermittent /fs/FileSystemFileHandle-writable-file-stream-lock-modes.https.tentative.worker.html | single tracking bug

Set release status flags based on info from the regressing bug 1850433

Set release status flags based on info from the regressing bug 1850433

Flags: needinfo?(aborovova)
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.