Skip to content
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

test: make sure current run result is pushed and reset #54332

Merged

Conversation

jakecastelli
Copy link
Member

@jakecastelli jakecastelli commented Aug 12, 2024

Because the currentRun result is only pushed into runs after the second test run finished, therefore all the runs array's length is 1 (with 2 runs results concat into 1 big string). Added assertion to make sure runs have the correct length (number of runs).

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/test_runner

@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 Aug 12, 2024
@jakecastelli jakecastelli force-pushed the fix-result-push-and-reset branch from 59e3f97 to 60b8da8 Compare August 12, 2024 15:09
@jakecastelli jakecastelli force-pushed the fix-result-push-and-reset branch from 60b8da8 to 73acd48 Compare August 12, 2024 15:53
@@ -12,6 +12,9 @@ import { join } from 'node:path';
if (common.isIBMi)
common.skip('IBMi does not support `fs.watch()`');

if (common.isAIX)
Copy link
Member Author

@jakecastelli jakecastelli Aug 12, 2024

Choose a reason for hiding this comment

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

I had a rough time with CI on AIX previously, I don't know if we should skip it entirely or just skip the test that has 100% failure rate due to the platform limitation (in this case the file deletion test)

Copy link

codecov bot commented Aug 12, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.08%. Comparing base (0301309) to head (73acd48).
Report is 419 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #54332      +/-   ##
==========================================
- Coverage   87.09%   87.08%   -0.02%     
==========================================
  Files         647      647              
  Lines      181889   181930      +41     
  Branches    34884    34899      +15     
==========================================
+ Hits       158420   158433      +13     
- Misses      16773    16779       +6     
- Partials     6696     6718      +22     

see 32 files with indirect coverage changes

Copy link
Contributor

@cjihrig cjihrig 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 the CI passes.

@jakecastelli jakecastelli added the request-ci Add this label to start a Jenkins CI on a PR. label Aug 13, 2024
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Aug 13, 2024
@nodejs-github-bot
Copy link
Collaborator

@jakecastelli jakecastelli added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Aug 14, 2024
Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

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

lgtm

@mcollina mcollina added commit-queue Add this label to land a pull request using GitHub Actions. and removed commit-queue Add this label to land a pull request using GitHub Actions. labels Aug 14, 2024
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Aug 14, 2024
@nodejs-github-bot nodejs-github-bot merged commit c1ec099 into nodejs:main Aug 14, 2024
61 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in c1ec099

RafaelGSS pushed a commit that referenced this pull request Aug 19, 2024
PR-URL: #54332
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
@RafaelGSS RafaelGSS mentioned this pull request Aug 19, 2024
@targos targos added the dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. label Sep 21, 2024
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. dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. 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.

5 participants