-
Notifications
You must be signed in to change notification settings - Fork 166
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
node-test-commit-linuxone cannot find ./build/jenkins/scripts/select-compiler.sh #1501
Comments
Ah https://ci.nodejs.org/job/node-test-commit-linuxone/nodes=rhel72-s390x/5296/ looks okay... looks like all the failures are on test-linuxonecc-rhel72-s390x-1. |
Still not quite sure how this is working, other than perhaps the file is somehow already in the workspace (and perhaps for some reason the workspace on test-linuxonecc-rhel72-s390x-1 was wiped)? |
Found the change: https://ci.nodejs.org/job/node-test-commit-linuxone/jobConfigHistory/showDiffFiles?timestamp1=2018-08-19_22-06-16×tamp2=2018-09-04_16-27-36 So the job was broken at the beginning of the month and is only working because the workspace(s) haven't been wiped until now. |
From #node-build:
|
It seems that today something has changed and node-test-commit-linuxone has started to fail due to:
e.g. https://ci.nodejs.org/job/node-test-commit-linuxone/5292/nodes=rhel72-s390x/console
I had a quick look through the job configuration history https://ci.nodejs.org/job/node-test-commit-linuxone/jobConfigHistory/ but there's nothing to indicate a configuration change in the time frame that the jobs started to fail:
I can't see anything in the current job configuration that actually clones/pulls down neither the build git repository nor the script in question directly (which explains why it's not working now but not how it worked in the first place).
cc @nodejs/platform-s390
The text was updated successfully, but these errors were encountered: