Test: Fix npm v8 related issues, improve reliablity of Windows testing #10252
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When error happens on set comparision, no difference is shown. Switch to compare arrays
Codecov Report
@@ Coverage Diff @@
## master #10252 +/- ##
=======================================
Coverage 85.38% 85.39%
=======================================
Files 339 339
Lines 13838 13840 +2
=======================================
+ Hits 11816 11819 +3
+ Misses 2022 2021 -1
Continue to review full report at Codecov.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After switching integration testing on v3 branch to Node.js v16, package integration tests started to fail. It's due to npm v8 leaving more files behind.
Additionally, ensure the reliability of Windows tests. Discovered that some tests fail on my side, due to slightly different environmental characteristics.