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 took test-osuosl-aix61-ppc64_be-2 offline because it running node-test-commit-aix was a sea of red with failures on parallel/test-repl-envvars. I think this is a build thing and not a test issue. Anyone have any better information on that, though?
@gireeshpunathil once you figure out what is going on please get either @refack or @gibfahn to help make the change on the machine that was disabled/reenable.
@refack I've been told its not really expected that AIX machines are rebooted often like you would with linux machines. It is the recommendation of our AIX contact that we only do it when absolutely necessary... Likely not an issue but just to ask that we don't do it too often.
One, other thing to consider is if the rest of the tests pass, and its going to take a while to figure out what the issue is with this specific test, one option is to exclude the test. Even though we have the other machine we should keep an eye on whether we end up with a big backlog because we are down to a single machine.
Going to leave enabled. The only difference between the passing and previous failing run was me killing and restarting the agent so I'm hoping that is what caused the passing run and means the jobs will continue to pass on the machine as well.
Activity
mhdawson commentedon Nov 7, 2017
@gireeshpunathil once you figure out what is going on please get either @refack or @gibfahn to help make the change on the machine that was disabled/reenable.
refack commentedon Nov 7, 2017
That server I bonkers.
parallel/test-repl-envvarspasses as is ontest-osuosl-aix61-ppc64_be-1Please don't bring on-line until it's fixed
refack commentedon Nov 7, 2017
P.S. I even rebooted, and it didn't help.
mhdawson commentedon Nov 8, 2017
@refack I've been told its not really expected that AIX machines are rebooted often like you would with linux machines. It is the recommendation of our AIX contact that we only do it when absolutely necessary... Likely not an issue but just to ask that we don't do it too often.
mhdawson commentedon Nov 8, 2017
One, other thing to consider is if the rest of the tests pass, and its going to take a while to figure out what the issue is with this specific test, one option is to exclude the test. Even though we have the other machine we should keep an eye on whether we end up with a big backlog because we are down to a single machine.
mhdawson commentedon Nov 8, 2017
@gibfahn I think @gireeshpunathil may already have access to the AIX machines but if not can you facilitate that.
mhdawson commentedon Nov 8, 2017
Ran the test manually on the machine and it passed:
mhdawson commentedon Nov 8, 2017
Trying in the CI to see if it still fails when run that way: https://ci.nodejs.org/job/node-test-commit-aix/10102/nodes=aix61-ppc64/console
mhdawson commentedon Nov 8, 2017
Seems to have failed in CI. Going to kill and restart the jenkins agent in case it is related to how it was started
mhdawson commentedon Nov 8, 2017
Passed in this run: https://ci.nodejs.org/job/node-test-commit-aix/nodes=aix61-ppc64/10103/console.
My only guess may be that it might somehow be related to how the jenkins agent is started.
What I used was (and have used in the past):
And to be more precise I usually cd into etc/rc.d/rc2.d and then run sh S20jenkins start
I wonder if there is something subtly different when it gets started automatically on reboot.
mhdawson commentedon Nov 8, 2017
Going to leave enabled. The only difference between the passing and previous failing run was me killing and restarting the agent so I'm hoping that is what caused the passing run and means the jobs will continue to pass on the machine as well.
refack commentedon Nov 8, 2017
https://ci.nodejs.org/computer/test-osuosl-aix61-ppc64_be-2/builds

Looking good 👍
refack commentedon Nov 8, 2017
Closing as this seems resolved.
Summary: