-
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
update NODE_VERSION choices for nodereport-continuous-integration #1421
Comments
I believe that I have permissions to save changes to the config for this job (that is, the |
Running some jobs to test. |
Started https://ci.nodejs.org/job/nodereport-continuous-integration/215/ against Node.js v10. Apart from the expected Windows failures, the following are also failing:
I think we need to update the job to be smarter about what platforms to build on. The current job config is using this wonderfully convoluted combination filter: Maybe this can be replaced with jenkins/scripts/VersionSelectorScript.groovy? The job may also need to call jenkins/scripts/select-compiler.sh. |
For v11.0.0-nightly: https://ci.nodejs.org/job/nodereport-continuous-integration/216/ |
Headers issue should now be resolved https://nodejs.org/download/nightly/v11.0.0-nightly20180731be322bd9ad/?d=10 |
https://ci.nodejs.org/job/nodereport-continuous-integration/217/ now has a varity of actual failures. One that is build related is v10-11 do not include linux-32 binaries.
|
Update: I'm still looking at this. It looks like there's quite a bit of refactoring I would need to do to the job in terms of parameter/matrix names to be able to use the VersionSelectorScript.
|
You might look at the job for https://ci.nodejs.org/view/x%20-%20Abi%20stable%20module%20API/job/node-test-node-addon-api/. It most likely needs to run on the same set of Node version/os version combinations. |
Hmm tried to use VersionSelectorScript but getting a permissions error:
|
Thanks to @refack for sorting the permissions. |
With Node 10: https://ci.nodejs.org/job/nodereport-continuous-integration/228/ rhel72-s390x failed to run
smartos16-64 failed to run
ubuntu1404-32 not skipped (probably an issue for the VersionSelectorScript). |
Node.js v11.0.0-nightly failed due to missing headers tarball (and missing mac os binaries): https://ci.nodejs.org/job/nodereport-continuous-integration/230/ |
Sounds like the invocation of the compiler selection script is needed to address the GLIBCXX issue, and likely needs the addition from #1265 (which I hope to land soo, just want to be very careful as it would have broken all of our release binaries in its first version :)). |
Being addressed in #1498. |
Definitely looks like we'll need #1265. https://ci.nodejs.org/job/nodereport-continuous-integration/233/nodes=rhel72-s390x/console + rm -rf build
+ git clone https://github.com/nodejs/build.git
Cloning into 'build'...
+ . ./build/jenkins/scripts/select-compiler.sh
++ '[' '' '!=' DONT ']'
++ case $NODE_NAME in
++ SELECT_ARCH=S390X
++ '[' S390X = PPC64LE ']'
++ '[' S390X = S390X ']'
++ export COMPILER_LEVEL=
++ COMPILER_LEVEL=
+++ python tools/getnodeversion.py
python: can't open file 'tools/getnodeversion.py': [Errno 2] No such file or directory
++ NODE_VERSION=
Build step 'Conditional steps (multiple)' marked build as failure |
Now that #1265 has been merged we have the following for Node.js 10: Windows failures are expected (nodejs/node-report#113). The smartos16-64 failure looks to be the following https://github.com/nodejs/node/blob/master/BUILDING.md#fn1:
|
With Node.js 8: 🎉 |
@richardlau if you look at the build job for n-api we only tests certain node versions on certain smartos images. Is that possibly the issue? |
I've removed One final build: https://ci.nodejs.org/job/nodereport-continuous-integration/257/ |
|
Current choices for
NODE_VERSION
in https://ci.nodejs.org/view/post-mortem/job/nodereport-continuous-integration/ are:This issue tracks the following changes:
v10
v9.0.0-nightly
withv11.0.0-nightly
Note that currently node-report is reported broken on Windows after the recent libuv update in v10.7.0 and master (i.e. the v11.0.0 nightlies): nodejs/node-report#113
The text was updated successfully, but these errors were encountered: