-
Notifications
You must be signed in to change notification settings - Fork 151
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
lookup: skip graceful-fs on >=11 #655
Conversation
Codecov Report
@@ Coverage Diff @@
## master #655 +/- ##
=======================================
Coverage 94.41% 94.41%
=======================================
Files 26 26
Lines 823 823
=======================================
Hits 777 777
Misses 46 46 Continue to review full report at Codecov.
|
Some tests fail because of GC-related changes.
858f0cd
to
4650873
Compare
Do you remember what was decided during the latest breakage of graceful-fs? We might need to open an issue there and get this fixed. cc @addaleax. |
Feel free to open an issue there, I agree it should be done. In the mean time, I want to get CITGM runs green again. Otherwise it's too difficult to determine if a change in core introduces new breakages. |
I tend to disagree with the overall approach. Skipping modules that fails provides a false sense of security “but citgm was green!” I think we should open an issue “Ecosystem modules that will break on Node 12.0.0” in core, and append these to the list. So that we keep track of what has been skipped and must be fixed. |
SGTM |
@mcollina This is a different kind of breakage than the issues we were having with them hooking into our internals – see isaacs/node-graceful-fs#137 for the root cause here |
@mcollina I opened nodejs/node#25060. LGTY? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
lol nodejs/node#25059 ;). |
Some tests fail because of GC-related changes.