| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
We should land this ASAP (once CI passes) to fix CI on windows master. cc/ @nodejs/platform-windows |
Sorry, something went wrong.
|
I hate the \r\n EOF mess. |
Sorry, something went wrong.
|
LGTM if the CI is green |
Sorry, something went wrong.
|
This LGTM as-is, although I think I'd prefer assert.strictEqual(c.stderr.trim(), ...);. That would provide a more helpful message in the event that the assertion fires. |
Sorry, something went wrong.
|
@Trott I agree that would have been better, but for now I think I'm going to land this as-is so that the build on master can be fixed ASAP. I can follow up with another PR to improve the error message. |
Sorry, something went wrong.
The test introduced in a5f91ab accidentally introduced failures on some windows builds. Update the assertion that was causing the failures. PR-URL: nodejs#12212 Ref: nodejs#11689 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Sorry, something went wrong.
|
This fixes a bug that was introduced in a semver-major commit -- it doesn't seem like it makes sense to backport. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
The test introduced in a5f91ab accidentally introduced failures on some windows builds. Update the assertion that was causing the failures.
Ref: #11689
Checklist
Affected core subsystem(s)
test