-
Notifications
You must be signed in to change notification settings - Fork 167
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
citgm/stress jobs do not select compiler for AIX on v10.x/master #1254
Comments
This apparently goes for CITGM as well: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/1390/nodes=rhel72-s390x/console |
Work around nodejs/build#1254, which effectively breaks stress test CI and CITGM, by avoiding `std::make_unique` for now. This workaround should be reverted once that issue is resolved. Refs: nodejs/build#1254
Work around nodejs/build#1254, which effectively breaks stress test CI and CITGM, by avoiding `std::make_unique` for now. This workaround should be reverted once that issue is resolved. Refs: nodejs/build#1254 PR-URL: #20386 Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com> Reviewed-By: Matheus Marchini <matheus@sthima.com>
Fixing the stress job. @gdams can you update the CITGM jobs, they need to use
For all platforms (selection is currently done on PPC, s390 and AIX, but will be on others in the future). In addition for AIX if there is a CC= definition it should be removed as that is now set by the selection script. |
Stress job fixed. |
Work around nodejs/build#1254, which effectively breaks stress test CI and CITGM, by avoiding `std::make_unique` for now. This workaround should be reverted once that issue is resolved. Refs: nodejs/build#1254 PR-URL: #20386 Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com> Reviewed-By: Matheus Marchini <matheus@sthima.com>
Ping @gdams re. the CitGM jobs ^ Note that this is affecting the v10.2.0 PR: nodejs/node#20724 (comment) |
@gdams can you prioritize updating the Citgm jobs? |
I have added this script to the citgm-smoker job |
thanks all! Can this be considered fixed now? |
@gdams did you test with a citgm run? I think we want to do that and then we can close. The key thing is to make sure that the job selects the right compiler based on the Node.js version. If the job builds node.js from source then it should do the right thing. For jobs that use existing binaries it needs an extra step that I added to the job for the tests for the node-addon-api. |
I think the CitGM jobs may need more work. From the latest v10.2.0 CitGM runs: rhel72-s390x
https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/1435/nodes=rhel72-s390x/consoleFull aix61-ppc64
https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/1435/nodes=aix61-ppc64/console We shouldn't be attempting to build Node.js 10 on AIX 6.1 as the minimum supported level is 7.1 TL04: https://github.com/nodejs/node/blob/v10.0.0/BUILDING.md#supported-platforms |
@richardlau, while in the perfect world you are correct for Node 10.x the reality is that we don't have the hw at this point and building on 6.1 is what we need to do. We made the minimum level 7.1 to that we'd have the flexibility of moving up to that but we are not planning to build the infrastructure in the near future so we SHOULD continue to build 10.x on AIX 6.1 for now. |
@mhdawson ack. The CitGM job is failing on AIX with the compiler script though. |
@gdams the problem with the runs shown for 9.x and 10.x above is that previously CC was set in the configure step. When I updated the other jobs I had to remove that as CC is now set in the compiler selection script. I'm guessing that if the original set of CC is still there it is overwriting what the script had put in place. |
@gdams do you have a timeline for when you might be able to look at this? |
One problem was that the LIBPATH was being unset after the selection, moved it to be after and we'll see if that helps. @gdams I only changed this job https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/ so others probably need the same change. |
Looks to have run much further, but still compiling. |
so I can see the following failure on the aix jobs: + . ./build/jenkins/scripts/select-compiler.sh
+ [ != DONT ]
+ SELECT_ARCH=AIXPPC
+ [ AIXPPC = PPC64LE ]
+ [ AIXPPC = S390X ]
+ [ AIXPPC = AIXPPC ]
+ + python tools/getnodeversion.py
python: can't open file 'tools/getnodeversion.py': [Errno 2] No such file or directory
NODE_VERSION= I'll take a look at what's going wrong |
I fixed it up and seems to be ok now, had to do with the current directory when the selection was being done. |
It now ran ok I believe but like other platforms there are failures. https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/1445/nodes=aix61-ppc64/console @gdams can you see if these match the other platforms. If so I think we can close this issue. |
I'm still seeing this failure on s390x: + node -v
node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by node) https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/nodes=rhel72-s390x/1446/console |
This was fixed by #1548. |
Refs: nodejs/node#20137 (comment)
The stress job appears not to be using the compiler selector script added by #1240 so it's using the wrong level of gcc on AIX for master/v10.x.
e.g., https://ci.nodejs.org/job/node-stress-single-test/1825/nodes=aix61-ppc64/consoleFull
The text was updated successfully, but these errors were encountered: