-
Notifications
You must be signed in to change notification settings - Fork 149
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: add npm #489
lookup: add npm #489
Conversation
If I recall correctly npm test suite wasn’t able to run in our CI… hopefully I’m incorrect :D
|
If I remember correctly, the main (only?) reason we’re not currently running it is that it makes a lot of network calls, but then again citgm isn’t exactly shy of doing that anyway… |
I assume we normally want to test the vendored copy of npm rather than My issue with this is that the npm tests have never passed for me on any platform other than macOS, and seem to be flaky there. See the latest runs of the CI jobs for an example. If we're going to have to mark it as flaky everywhere there's not much point in having it. |
@gibfahn I guess it would still be useful to have npm run in case the tests pass on OS-X. So we could just skip them everywhere else. |
They're also flaky on macOS... If someone would like to raise a PR adding npm we can run citgm on it to test. I'm not strongly against adding npm, just skeptical of the benefits. |
@gibfahn I am not sure what PR you would want besides this one? |
Sorry, got my wires crossed. Smoker run: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker-nobuild/239/ |
If we can run the npm tests at least on one system, I still think we should do that. |
on Linux:
|
Codecov Report
@@ Coverage Diff @@
## main #489 +/- ##
==========================================
- Coverage 96.12% 95.33% -0.80%
==========================================
Files 31 26 -5
Lines 929 900 -29
==========================================
- Hits 893 858 -35
- Misses 36 42 +6
Continue to review full report at Codecov.
|
Launched https://github.com/targos/citgm/actions/runs/627105955 to check the status. |
It's green! Let's try with more platforms: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker-pipeline/137/ |
The failure on LinuxONE (s390x) is tapjs/tapjs#691, the underlying cause being emscripten currently lacking support for big endian systems (emscripten-core/emscripten#12387). |
This was, surprisingly, not in this list.
Rebased and skipped s390. |
This was, surprisingly, not in this list. Also, I am not sure, but I guess this shouldn’t be merged as long as
npm
is broken on nodemaster
?Checklist
npm test
passes