-
Notifications
You must be signed in to change notification settings - Fork 150
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: declare bankruptcy on flaky modules #959
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -55,10 +55,6 @@ | |
"prefix": "v", | ||
"skip": ["win32", "aix"] | ||
}, | ||
"bluebird": { | ||
"prefix": "v", | ||
"maintainers": "petkaantonov" | ||
}, | ||
"body-parser": { | ||
"flaky": "aix", | ||
"maintainers": "dougwilson" | ||
|
@@ -90,7 +86,7 @@ | |
"maintainers": "mcollina", | ||
"flaky": ["rhel"], | ||
"prefix": "v", | ||
"skip": ["aix", "win32"] | ||
"skip": ["aix", "darwin", "win32"] | ||
}, | ||
"coffeescript": { | ||
"maintainers": ["jashkenas", "GeoffreyBooth"], | ||
|
@@ -153,19 +149,10 @@ | |
"expectFail": "fips", | ||
"skip": ["win32"] | ||
}, | ||
"express": { | ||
"flaky": "ppc", | ||
"maintainers": "dougwilson", | ||
"skip": "win32" | ||
}, | ||
"express-session": { | ||
"prefix": "v", | ||
"maintainers": "dougwilson" | ||
}, | ||
"fastify": { | ||
"maintainers": ["mcollina", "delvedor"], | ||
"prefix": "v" | ||
}, | ||
"flush-write-stream": { | ||
"prefix": "v", | ||
"maintainers": "mafintosh", | ||
|
@@ -214,10 +201,6 @@ | |
"maintainers": "contra", | ||
"skip": "win32" | ||
}, | ||
"https-proxy-agent": { | ||
"maintainers": "TooTallNate", | ||
"scripts": ["build", "test"] | ||
}, | ||
"iconv": { | ||
"prefix": "v", | ||
"flaky": "aix", | ||
|
@@ -235,6 +218,7 @@ | |
}, | ||
"is-core-module": { | ||
"prefix": "v", | ||
"skip": "win32", | ||
"maintainers": "ljharb", | ||
"scripts": ["tests-only"] | ||
}, | ||
|
@@ -310,11 +294,13 @@ | |
}, | ||
"mime": { | ||
"prefix": "v", | ||
"maintainers": "broofa" | ||
"maintainers": "broofa", | ||
"skip": "win32" | ||
}, | ||
"minimist": { | ||
"npm": true, | ||
"maintainers": "substack" | ||
"skip": "win32", | ||
"maintainers": "ljharb" | ||
}, | ||
"mkdirp": { | ||
"head": true, | ||
|
@@ -358,11 +344,6 @@ | |
"comment": "Flaky because of test timeouts", | ||
"skip": true | ||
}, | ||
"npm": { | ||
"maintainers": ["nodejs/npm"], | ||
"prefix": "v", | ||
"skip": ["aix", "s390"] | ||
}, | ||
"path-to-regexp": { | ||
"prefix": "v", | ||
"maintainers": "blakeembrey", | ||
|
@@ -386,11 +367,6 @@ | |
"comment": "Error message changes in V8 9.3", | ||
"repo": "https://github.com/pugjs/pug" | ||
}, | ||
"pump": { | ||
"prefix": "v", | ||
"maintainers": "mafintosh", | ||
"skip": "win32" | ||
}, | ||
"pumpify": { | ||
"prefix": "v", | ||
"maintainers": "mafintosh", | ||
|
@@ -426,17 +402,8 @@ | |
}, | ||
"rewire": { | ||
"prefix": "v", | ||
"maintainers": "jhnns" | ||
}, | ||
"rimraf": { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. rimraf: Failing because ts-node doesn't work on node 20. |
||
"prefix": "v", | ||
"flaky": "win32", | ||
"maintainers": "isaacs" | ||
}, | ||
"router": { | ||
"prefix": "v", | ||
"maintainers": "dougwilson", | ||
"skip": "win32" | ||
"maintainers": "jhnns", | ||
"scripts": ["test -- --timeout 30000"] | ||
}, | ||
"sax": { | ||
"skip": "win32", | ||
|
@@ -454,10 +421,8 @@ | |
}, | ||
"serialport": { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. All our tests work reliably on node20, runtime libuv however not so much but it would not be seen here as it needs hardware to run. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. looks like serialport's failures are due to macos disk space - happy to drop macos from the citgm There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. serialport is one of the few where we probably don't want to skip macOS if we can avoid it, but certainly skipping that one OS is better than complete removal. I'll add it back in and also remove the skip for Windows and run a CITGM. If it fails on Windows and/or macOS but nowhere else, we'll skip those but leave it alone otherwise. (Sorry our macOS test machines are not as robustly provisioned as we might like. Alas, we run on donated services, etc.) |
||
"prefix": "serialport@", | ||
"flaky": ["ppc", "rhel"], | ||
"tags": "native", | ||
"maintainers": "reconbot", | ||
"skip": ["win32"] | ||
"maintainers": "reconbot" | ||
}, | ||
"socket.io": { | ||
"maintainers": "rauchg", | ||
|
@@ -497,7 +462,9 @@ | |
"tape": { | ||
"head": true, | ||
"prefix": "v", | ||
"maintainers": "substack" | ||
"skip": "win32", | ||
"scripts": ["tests-only"], | ||
"maintainers": "ljharb" | ||
}, | ||
"thread-sleep": { | ||
"install": ["install", "--build-from-source"], | ||
|
@@ -521,9 +488,6 @@ | |
"prefix": "v", | ||
"maintainers": "mafintosh" | ||
}, | ||
"tough-cookie": { | ||
"maintainers": ["awaterma", "colincasey", "ruoho", "wjharney"] | ||
}, | ||
"uglify-js": { | ||
"prefix": "v", | ||
"flaky": ["ppc", "darwin"], | ||
|
@@ -537,10 +501,6 @@ | |
"maintainers": "jashkenas", | ||
"ignoreGitHead": true | ||
}, | ||
"undici": { | ||
"prefix": "v", | ||
"maintainers": ["mcollina", "ronag"] | ||
}, | ||
"uuid": { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I just release There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'll add it back in and re-run CITGM. 🤞 |
||
"prefix": "v", | ||
"maintainers": ["ctavan", "broofa"], | ||
|
@@ -568,13 +528,10 @@ | |
"maintainers": "tootallnate", | ||
"tags": "native" | ||
}, | ||
"winston": { | ||
"flaky": ["win32", "ppc", "s390", "darwin"], | ||
"maintainers": "indexzero" | ||
}, | ||
"ws": { | ||
"expectFail": "fips", | ||
"maintainers": ["einaros", "3rd-Eden", "lpinca"] | ||
"maintainers": ["einaros", "3rd-Eden", "lpinca"], | ||
"scripts": ["test -- --timeout 30000"] | ||
}, | ||
"yargs": { | ||
"comment": "Install from source is currently broken due to TS error", | ||
|
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.
I looked into this: there is no issue with Node 20. The test passes on GitHub. The tests have been working fine for a couple of years. The test is also not asynchronous or contains any randomness.
The failing test is testing the TypeScript integration, which took 300ms on my machine and takes 1.2s on GitHub. My assumption is that the test timeout of 2s is too aggressive for more expensive tests in combination with a busy CPU.
What's the recommendation in that case? How can I address this? :)
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.
Any recommendation? :)
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.
I think we can use the
"script"
setting in CITGM to pass a longer timeout via CLI tomocha
. Like maybenpm run test --timeout 5000
will work?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.
I'll try that and run CITGM and see what happens.
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.
Yes, passing
npm run test -- --timeout 5000
works. I've just tested it :)