-
Notifications
You must be signed in to change notification settings - Fork 148
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
tape failing on multiple versions and platforms #895
Comments
Thanks, that's good to know. Luckily they're all issues with the dev-only eclint script, but it's still potentially masking real problems, so I'd love to fix it. It might be an issue with |
If I could get access to those machines, or if anyone can reproduce it on their machine, it'd be great to figure out what |
Seems plausible. We do have both ubuntu1804 and ubuntu1604 in the matrix on Jenkins and it's failing in the same way there too. But, that's possibly a difference in our host setup in Jenkins versus GH actions. Access to the linux machines should be much easier to distribute than Windows ones you requested in nodejs/build#2913. I don't have access myself, and I am not sure how quickly the tmp directories are cleaned up so some manual steps may be needed to recreate. |
Should i file an issue for one of these too? |
Sure, or maybe you could rename nodejs/build#2913 to be a generic request and request an additional os/arch within there? I don't personally see the need to gather approvals for your access on a per platform basis, but would defer to @nodejs/build for whatever makes their access management easier. |
@ljharb I got a little creative with our Jenkins job and managed to get the output of that command in the output - see https://ci.nodejs.org/job/citgm-smoker-nobuild/nodes=ubuntu1804-64/1159/consoleText |
FWIW I don't think
https://github.com/substack/tape/archive/HEAD.tar.gz doesn't contain a FWIW we could make CITGM use git to clone tape rather than use the tarball using the diff --git a/lib/lookup.json b/lib/lookup.json
index 1f43084..d19636d 100644
--- a/lib/lookup.json
+++ b/lib/lookup.json
@@ -506,7 +506,8 @@
"tape": {
"head": true,
"prefix": "v",
- "maintainers": "substack"
+ "maintainers": "substack",
+ "useGitClone": "true"
},
"thread-sleep": {
"install": ["install", "--build-from-source"], |
ahhhhh well yeah, if you're using the tarball then it's not necessarily going to include all the files needed to run the tests. Seems like the simplest option is to enable |
Although, I'll first change |
alrighty - try tape-testing/tape@5f78134 and hopefully that will gracefully avoid the eclint failure when there's no |
That seems to have worked 🎉 - https://ci.nodejs.org/job/citgm-smoker-nobuild/nodes=ubuntu1804-64/1163/console |
yay! let's just stick with that then. Thanks for the error output, and thanks to @richardlau for figuring out the source of the problem :-) Is this OK to close? |
Actually, windows is still unhappy:
|
ha, fun, env vars and also subcommands are linux-only commands. i'll see if i can figure out a clean way to make that script a noop on windows. |
@BethGriggs at your convenience, please run another windows build - i think the latest commit should solve it. |
It seems to have gotten much further, but still bailing out of the job at the end on Windows 🤔 - https://ci.nodejs.org/job/citgm-smoker-nobuild/nodes=win10-vs2019/1171/consoleText |
im not sure what that means; node is clearly there since eslint just ran prior, but the tests aren’t finding it? |
I got the access I needed in nodejs/build#2913, and I think I fixed this with tape-testing/tape@3e7b2ae - any chance someone can let me know if the next CIGTM run still has this failure? update: nvm, this might not be fixed yet; still working on it. |
Extracting this from #894 because I have discovered that there are different failures across multiple versions/platforms.
Most platforms fail with this error [Resolved]:
Windows bails out earlier with a separate error:
Interestingly macOS and AIX seem to consistently pass:
Test run links:
The text was updated successfully, but these errors were encountered: