Skip to content

test: remove --no-warnings flag #58424

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

tniessen
Copy link
Member

This change should have no effect since the test does not appear to emit any warnings. If there are warnings, we probably should handle them properly instead of passing this flag to the runtime.

Refs: #35093

This change should have no effect since the test does not appear to
emit any warnings. If there are warnings, we probably should handle
them properly instead of passing this flag to the runtime.

Refs: nodejs#35093
@tniessen tniessen added crypto Issues and PRs related to the crypto subsystem. test Issues and PRs related to the tests. labels May 22, 2025
@nodejs-github-bot nodejs-github-bot added the needs-ci PRs that need a full CI run. label May 22, 2025
Copy link

codecov bot commented May 22, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.22%. Comparing base (53944c4) to head (d25a474).
Report is 46 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #58424      +/-   ##
==========================================
+ Coverage   90.21%   90.22%   +0.01%     
==========================================
  Files         635      635              
  Lines      187171   187174       +3     
  Branches    36748    36750       +2     
==========================================
+ Hits       168851   168879      +28     
+ Misses      11069    11063       -6     
+ Partials     7251     7232      -19     

see 35 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.

@tniessen tniessen added the request-ci Add this label to start a Jenkins CI on a PR. label May 23, 2025
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label May 23, 2025
@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot
Copy link
Collaborator

@tniessen
Copy link
Member Author

CI failed in a OpenSSL 1.1.1 FIPS configuration, but it seems infrastructure related:

Build timed out (after 60 minutes). Marking the build as failed.

@nodejs-github-bot
Copy link
Collaborator

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

Landed in affec48

targos pushed a commit that referenced this pull request May 31, 2025
This change should have no effect since the test does not appear to
emit any warnings. If there are warnings, we probably should handle
them properly instead of passing this flag to the runtime.

Refs: #35093
PR-URL: #58424
Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crypto Issues and PRs related to the crypto subsystem. 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