Skip to content

[FSA] Mark locking scheme WPTs as non-tentative #43134

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Nov 13, 2023

Marks the locking scheme WPTs as non-tentative.

Bug: 1382215
Change-Id: I9c18679d2a24762223d5923dfb148cbd3b1b10c1
Reviewed-on: https://chromium-review.googlesource.com/5027736
WPT-Export-Revision: 3f160fb1d7230bf2771b7fbde755a6ac14e20845

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

@chromium-wpt-export-bot chromium-wpt-export-bot changed the title Mark locking scheme WPTs as non-tentative [FSA] Enable Locking Scheme by default Nov 29, 2023
@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-5027736 branch 3 times, most recently from 2b73b67 to 0fc0d98 Compare December 4, 2023 22:05
@chromium-wpt-export-bot chromium-wpt-export-bot changed the title [FSA] Enable Locking Scheme by default [FSA] Mark locking scheme WPTs as non-tentative Dec 6, 2023
Marks the locking scheme WPTs as non-tentative.

Bug: 1382215
Change-Id: I9c18679d2a24762223d5923dfb148cbd3b1b10c1
@chromium-wpt-export-bot
Copy link
Collaborator Author

Close this PR because the Chromium CL has been abandoned.

@chromium-wpt-export-bot chromium-wpt-export-bot deleted the chromium-export-cl-5027736 branch April 16, 2025 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants