You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I seem to recall that years ago, during the first ports to AIX, that there was a problem with python involving ptys. @gireeshpunathil or @richardlau, you were around then, do you remember this?
I seem to recall that years ago, during the first ports to AIX, that there was a problem with python involving ptys. @gireeshpunathil or @richardlau, you were around then, do you remember this?
@refack just to be clear, python tools/test.py --report pseudo-tty is how to repro the issue, but its not what we are actually doing in CI? I ask, because if we were doing that, a possible workaround would be to just stop using --report pseudo-tty.
@sam-github, yes. --report pseudo-tty are two independent args --report is just informative, pseudo-tty is a positional arg telling the harness which suite to run.
I'm not sure how to read the following failures, they have the same timed out after 10 minutes message, but they did NOT timeout during a tools/test.py run... So, does that mean the problem is not related to tools/test.py and python and PTYs? Or does it mean there are two problems?
ppc64/out/Release/obj.target/tools/v8_gypfiles/libv8_libsampler.a /home/iojs/build/workspace/node-test-commit-aix/nodes/aix61-ppc64/out/Release/obj.target/tools/v8_gypfiles/libv8_compiler.a /home/iojs/build/workspace/node-test-commit-aix/nodes/aix61-ppc64/out/Release/obj.target/tools/v8_gypfiles/libv8_initializers.a -latomic -ldl -lrt -lm -lperfstat
02:10:44 Build timed out (after 10 minutes). Marking the build as failed.
02:10:44 Build was aborted
@bnoordhuis This bug is easily reproduceable, as @refack says, you can do it via ssh:
ssh test-osuosl-aix61-ppc64_be-1
su - iojs
cd /home/iojs/build/workspace/node-stress-single-test/nodes/aix61-ppc64
export NODE_NAME=test-osuosl-aix61-ppc64_be-1
. ./build/jenkins/scripts/select-compiler.sh
time ./out/Release/node test/pseudo-tty/console-dumb-tty.js
# instantly completes
python tools/test.py -p tap --logfile testx.tap --mode=release pseudo-tty/console-dumb-tty
# hangs indefinitely
I added your key to the machine, see #1848, and I suspect the build above will sit around for a while (until the next time a node-stress-single-test is run on that machine, which doesn't happen by default).
Activity
richardlau commentedon Jun 4, 2019
Possibly related to nodejs/node#9728? cc @gireeshpunathil
mhdawson commentedon Jun 5, 2019
I think @sam-github has been looking at this one.
sam-github commentedon Jun 5, 2019
Nope, first I've heard of it.
I seem to recall that years ago, during the first ports to AIX, that there was a problem with python involving ptys. @gireeshpunathil or @richardlau, you were around then, do you remember this?
richardlau commentedon Jun 5, 2019
I think it was the nodejs/node#9728 I referenced earlier.
sam-github commentedon Jun 5, 2019
@refack just to be clear,
python tools/test.py --report pseudo-ttyis how to repro the issue, but its not what we are actually doing in CI? I ask, because if we were doing that, a possible workaround would be to just stop using--report pseudo-tty.refack commentedon Jun 5, 2019
@sam-github, yes.
--report pseudo-ttyare two independent args--reportis just informative,pseudo-ttyis a positional arg telling the harness which suite to run.I updated the recipe to:
refack commentedon Jun 5, 2019
sam-github commentedon Jun 6, 2019
richardlau commentedon Jun 6, 2019
https://ci.nodejs.org/computer/test-osuosl-aix61-ppc64_be-2/ (the problematic host) is currently offline (disconnected by @joyeecheung since this morning).
mhdawson commentedon Jun 7, 2019
@sam-github I guess its needs another look.
bnoordhuis commentedon Jun 21, 2019
I'll take this one.
sam-github commentedon Jun 21, 2019
I'm not sure how to read the following failures, they have the same timed out after 10 minutes message, but they did NOT timeout during a tools/test.py run... So, does that mean the problem is not related to tools/test.py and python and PTYs? Or does it mean there are two problems?
sam-github commentedon Jun 21, 2019
I reviewed all the failures on https://ci.nodejs.org/job/node-test-commit-aix/ from 23960 to 23988 and categorized by failure, and by node number (the
: #refers to....-be-#).during cc test compiles: Build timed out (after 10 minutes). Marking the build as failed.
during js tests: Build timed out (after 10 minutes). Marking the build as failed.
Those last are possibly related to PTY issues, and I'm leaving them here in this issue.
Found also
sam-github commentedon Jun 24, 2019
@bnoordhuis This bug is easily reproduceable, as @refack says, you can do it via ssh:
I added your key to the machine, see #1848, and I suspect the build above will sit around for a while (until the next time a node-stress-single-test is run on that machine, which doesn't happen by default).
32 remaining items
test: specialize OOM check for AIX
test: specialize OOM check for AIX
test: specialize OOM check for AIX
Please ignore this msg (#1)
test: skip tests related to CI failures on AIX
test: fix pty test hangs on aix
test: specialize OOM check for AIX
test: fix pty test hangs on aix