Skip to content

test: mark web lock held test as flaky #59144

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

Merged

Conversation

IlyasShabi
Copy link
Contributor

@IlyasShabi IlyasShabi commented Jul 21, 2025

Refs: #59142

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/web-standards

@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. test Issues and PRs related to the tests. labels Jul 21, 2025
@IlyasShabi IlyasShabi marked this pull request as ready for review July 21, 2025 14:15
@IlyasShabi IlyasShabi requested a review from joyeecheung July 21, 2025 14:15
Copy link

codecov bot commented Jul 21, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.07%. Comparing base (3b57443) to head (4dd919a).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #59144      +/-   ##
==========================================
+ Coverage   90.04%   90.07%   +0.03%     
==========================================
  Files         648      648              
  Lines      191078   191078              
  Branches    37452    37454       +2     
==========================================
+ Hits       172050   172115      +65     
+ Misses      11649    11590      -59     
+ Partials     7379     7373       -6     

see 27 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@IlyasShabi IlyasShabi mentioned this pull request Jul 21, 2025
8 tasks
@joyeecheung joyeecheung added the fast-track PRs that do not need to wait for 48 hours to land. label Jul 21, 2025
Copy link
Contributor

Fast-track has been requested by @joyeecheung. Please 👍 to approve.

@joyeecheung

This comment was marked as resolved.

@joyeecheung
Copy link
Member

Oh wait, others are expected failures.

@IlyasShabi
Copy link
Contributor Author

@joyeecheung yes those are expected

@IlyasShabi IlyasShabi added the request-ci Add this label to start a Jenkins CI on a PR. label Jul 21, 2025
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jul 21, 2025
@nodejs-github-bot
Copy link
Collaborator

@aduh95 aduh95 added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. and removed fast-track PRs that do not need to wait for 48 hours to land. labels Jul 24, 2025
@nodejs-github-bot
Copy link
Collaborator

@panva panva force-pushed the ishabi/web-lock-held-flaky branch from e6a7ce2 to 4dd919a Compare July 27, 2025 08:16
@panva panva added the request-ci Add this label to start a Jenkins CI on a PR. label Jul 27, 2025
@panva
Copy link
Member

panva commented Jul 27, 2025

I'll look into the nature of these tests, it would appear the unhandled rejections are expected, so maybe all we need is to add a handler for the workers that execute the tests where this is expected. In the meantime, i've pushed my suggestion above which might actually work to ignore the flakyness.

@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jul 27, 2025
@nodejs-github-bot
Copy link
Collaborator

Copy link
Member

@targos targos left a comment

Choose a reason for hiding this comment

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

LGTM if it works.

@panva
Copy link
Member

panva commented Jul 27, 2025

Aside: the test harness does set up addEventListener("unhandledrejection") for these tests, which, i'm assuming, Node.js doesn't support? am I right?

@panva
Copy link
Member

panva commented Jul 27, 2025

LGTM if it works.

It does (tested locally by forcing an unhandled rejection in the wpt in question).

@nodejs-github-bot
Copy link
Collaborator

@panva panva added the commit-queue Add this label to land a pull request using GitHub Actions. label Jul 27, 2025
@nodejs-github-bot nodejs-github-bot added commit-queue-failed An error occurred while landing this pull request using GitHub Actions. and removed commit-queue Add this label to land a pull request using GitHub Actions. labels Jul 27, 2025
@nodejs-github-bot
Copy link
Collaborator

Commit Queue failed
- Loading data for nodejs/node/pull/59144
✔  Done loading data for nodejs/node/pull/59144
----------------------------------- PR info ------------------------------------
Title      test: mark web lock held test as flaky (#59144)
Author     Ilyas Shabi <[email protected]> (@IlyasShabi)
Branch     IlyasShabi:ishabi/web-lock-held-flaky -> nodejs:main
Labels     test, author ready, needs-ci
Commits    1
 - test: mark web lock held test as flaky
Committers 1
 - Filip Skokan <[email protected]>
PR-URL: https://github.com/nodejs/node/pull/59144
Refs: https://github.com/nodejs/node/issues/59142
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/59144
Refs: https://github.com/nodejs/node/issues/59142
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
--------------------------------------------------------------------------------
   ℹ  This PR was created on Mon, 21 Jul 2025 14:12:30 GMT
   ✔  Approvals: 3
   ✔  - James M Snell (@jasnell) (TSC): https://github.com/nodejs/node/pull/59144#pullrequestreview-3038872131
   ✔  - Filip Skokan (@panva) (TSC): https://github.com/nodejs/node/pull/59144#pullrequestreview-3059408069
   ✔  - Michaël Zasso (@targos) (TSC): https://github.com/nodejs/node/pull/59144#pullrequestreview-3059412213
   ✘  Last GitHub CI failed
   ℹ  Last Full PR CI on 2025-07-27T09:09:58Z: https://ci.nodejs.org/job/node-test-pull-request/68235/
- Querying data for job/node-test-pull-request/68235/
   ✔  Last Jenkins CI successful
--------------------------------------------------------------------------------
   ✔  Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/16550345467

@panva panva removed the commit-queue-failed An error occurred while landing this pull request using GitHub Actions. label Jul 27, 2025
@nodejs-github-bot
Copy link
Collaborator

@panva panva added the commit-queue Add this label to land a pull request using GitHub Actions. label Jul 27, 2025
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Jul 27, 2025
@nodejs-github-bot nodejs-github-bot merged commit cd1a90d into nodejs:main Jul 27, 2025
68 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in cd1a90d

aduh95 pushed a commit that referenced this pull request Jul 27, 2025
PR-URL: #59144
Refs: #59142
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
meteorqz6 pushed a commit to meteorqz6/node that referenced this pull request Aug 2, 2025
PR-URL: nodejs#59144
Refs: nodejs#59142
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. needs-ci PRs that need a full CI run. test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants