Closed Bug 1951329 Opened 18 days ago Closed 15 days ago

Perma linux ship [tier 2] /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | single tracking bug | After a file has finished moving, that file can have an open access handle in readwrite-unsafe mode - promise_rejects_dom

Categories

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

Product:
Core
Component:
DOM: File
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
138 Branch
Tracking Flags:
Tracking Status
firefox138 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: Sasha)

Details

(Keywords: intermittent-failure, intermittent-testcase)

Attachments

(1 file)

Bug 1951329 - Update test expectations for fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.js.
48 bytes, text/x-phabricator-request
Details | Review

Filed by: chorotan [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=497216480&repo=mozilla-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/BXefa3J9S2CYcZ3KCjPaAw/runs/0/artifacts/public/logs/live_backing.log

[task 2025-03-03T00:31:53.570Z] 00:31:53     INFO - TEST-KNOWN-INTERMITTENT-PASS | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | A file with an ongoing move operation does not interfere with an open access handle in readwrite-unsafe mode on another file 
[task 2025-03-03T00:31:53.571Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.571Z] 00:31:53     INFO - TEST-UNEXPECTED-FAIL | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | After a file has finished moving, that file can have an open access handle in readwrite-unsafe mode - promise_rejects_dom: function "function() { throw e }" threw object "NotFoundError: Entry not found" that is not a DOMException NoModificationAllowedError: property "code" is equal to 8, expected 7
[task 2025-03-03T00:31:53.571Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.572Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.572Z] 00:31:53     INFO - TEST-UNEXPECTED-PASS | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | A file cannot be moved to a location with an open access handle in readwrite-unsafe mode - expected NOTRUN
[task 2025-03-03T00:31:53.572Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.573Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.573Z] 00:31:53     INFO - TEST-UNEXPECTED-PASS | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | A file with an open access handle in readwrite-unsafe mode cannot be moved - expected NOTRUN
[task 2025-03-03T00:31:53.573Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.574Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.575Z] 00:31:53     INFO - TEST-UNEXPECTED-PASS | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | A file with an open access handle in readwrite-unsafe mode does not interfere with moving another file - expected NOTRUN
[task 2025-03-03T00:31:53.575Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.575Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.576Z] 00:31:53     INFO - TEST-UNEXPECTED-PASS | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | After an open access handle in readwrite-unsafe mode on a file has been closed, that file can be moved - expected NOTRUN
[task 2025-03-03T00:31:53.576Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.577Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.577Z] 00:31:53     INFO - TEST-UNEXPECTED-FAIL | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | A file with an ongoing remove operation does not interfere with the creation of an open access handle in readwrite-unsafe mode on another file - promise_test: Unhandled rejection with value: object "TypeError: fileHandle.remove is not a function"
[task 2025-03-03T00:31:53.578Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.578Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.579Z] 00:31:53     INFO - TEST-UNEXPECTED-FAIL | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | After a file has finished being removed, that file can have an open access handle in readwrite-unsafe mode - promise_test: Unhandled rejection with value: object "TypeError: fileHandle.remove is not a function"
[task 2025-03-03T00:31:53.580Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.581Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.582Z] 00:31:53     INFO - TEST-UNEXPECTED-FAIL | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | A directory cannot be removed if it contains a file that has an open access handle in readwrite-unsafe mode. - promise_test: Unhandled rejection with value: object "TypeError: fileHandle.remove is not a function"
[task 2025-03-03T00:31:53.582Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.583Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.584Z] 00:31:53     INFO - TEST-UNEXPECTED-FAIL | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | A file with an open access handle in readwrite-unsafe mode cannot be removed - promise_test: Unhandled rejection with value: object "TypeError: fileHandle.remove is not a function"
[task 2025-03-03T00:31:53.585Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.586Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.586Z] 00:31:53     INFO - TEST-UNEXPECTED-FAIL | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | A file with an open access handle in readwrite-unsafe mode does not interfere with removing another file - promise_test: Unhandled rejection with value: object "TypeError: fileHandle.remove is not a function"
[task 2025-03-03T00:31:53.587Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.588Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.589Z] 00:31:53     INFO - TEST-UNEXPECTED-FAIL | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | After an open access handle in readwrite-unsafe mode on a file has been closed, that file can be removed - promise_test: Unhandled rejection with value: object "TypeError: fileHandle.remove is not a function"
[task 2025-03-03T00:31:53.590Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.591Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.591Z] 00:31:53     INFO - TEST-UNEXPECTED-PASS | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | When there's an open writable stream in siloed mode on a file, cannot have an open access handle in readwrite-unsafe mode on that same file - expected NOTRUN
[task 2025-03-03T00:31:53.592Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.593Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.594Z] 00:31:53     INFO - TEST-UNEXPECTED-PASS | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | A file with an open writable stream in siloed mode does not interfere with an open access handle in readwrite-unsafe mode on another file - expected NOTRUN
[task 2025-03-03T00:31:53.594Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.595Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.596Z] 00:31:53     INFO - TEST-UNEXPECTED-PASS | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | After all writable streams in siloed mode have been closed for a file, that file can have an open access handle in readwrite-unsafe mode - expected NOTRUN
[task 2025-03-03T00:31:53.597Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.598Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.599Z] 00:31:53     INFO - TEST-UNEXPECTED-PASS | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | When there's an open access handle in readwrite-unsafe mode on a file, cannot open an open writable stream in siloed mode on that same file - expected NOTRUN
[task 2025-03-03T00:31:53.599Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.600Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.601Z] 00:31:53     INFO - TEST-UNEXPECTED-PASS | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | A file with an open access handle in readwrite-unsafe mode does not interfere with the creation of an open writable stream in siloed mode on another file - expected NOTRUN
[task 2025-03-03T00:31:53.602Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.603Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.603Z] 00:31:53     INFO - TEST-UNEXPECTED-PASS | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | When there's an open writable stream in exclusive mode on a file, cannot have an open access handle in readwrite-unsafe mode on that same file - expected NOTRUN
[task 2025-03-03T00:31:53.604Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN
[task 2025-03-03T00:31:53.605Z] 00:31:53     INFO - 
[task 2025-03-03T00:31:53.606Z] 00:31:53     INFO - TEST-UNEXPECTED-PASS | /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | A file with an open writable stream in exclusive mode does not interfere with an open access handle in readwrite-unsafe mode on another file - expected NOTRUN
[task 2025-03-03T00:31:53.606Z] 00:31:53     INFO - TEST-INFO | expected NOTRUN

Hello,

Could https://hg.mozilla.org/mozilla-central/rev/2cc3a051da20 cause this test to perma fail? Can you please take a look?

Retriggers and backfills here. The test is failing for each backfill.

Flags: needinfo?(aborovova)
Summary: Perma [tier 2] /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | single tracking bug | After a file has finished moving, that file can have an open access handle in readwrite-unsafe mode - promise_rejects_dom → Perma linux ship [tier 2] /fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.html | single tracking bug | After a file has finished moving, that file can have an open access handle in readwrite-unsafe mode - promise_rejects_dom
Flags: needinfo?(jjalkanen)

This is a new test for a feature whose specification proposal has not yet been merged. Currently we don't support readonly and readwrite-unsafe modes, they are going to be added by 1949462. The exclusive and siloed modes are the topic of 1840773 .

Additionally, according to the proposal, directories and the parent directories of a file should get an exclusive lock before moving or removing is possible, and these locks should automatically go away when the operation is complete. We will probably wait until the specification for these features has been merged.

The tests can be disabled for now or the bot may flag them as expected failures in the related configuration.

Flags: needinfo?(jjalkanen)
Assignee: nobody → aborovova
Status: NEW → ASSIGNED
Flags: needinfo?(aborovova)
Pushed by aborovova@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9960a15bc3c2 Update test expectations for fs/FileSystemFileHandle-cross-primitive-locking.https.tentative.worker.js. r=dom-storage-reviewers,edenchuang

https://hg.mozilla.org/mozilla-central/rev/9960a15bc3c2

Status: ASSIGNED → RESOLVED
Closed: 15 days ago
status-firefox138: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 138 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: