User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.8.1
The only useful information that I spot now is that it fails at
the first start-domain itself, which supports your assumption. (We
start the domain several times in the script). The pods(I used the
term node incorrectly before) are randomly assigned for
the tck pipelines. We don't know how to confirm if the failure
occur in same kubernetes pod.
If you were able to confirm failure occurs in same node/pod
repeatedly, then its a possible bug for eclipse infra.
On 11/06/20 11:43 pm, arjan tijms
wrote:
Hi,
Do you have any idea what it could be? I race condition
would be unlikely, since it keeps failing on the same node if
repeated. So maybe it's something related to the node, but I'm
not sure.
We encountered the same issue with jakartaee-tck platform
run too yesterday in couple of the nodes. But it went
through in all other >30 nodes.
+ /root/ri/glassfish6/glassfish/bin/asadmin --user
admin --passwordfile /root/admin-password.txt
start-domain Picked up JAVA_TOOL_OPTIONS: -Xmx6G Waiting for domain1 to start
........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ No response from the Domain Administration Server
(domain1) after 600 seconds. The command is either taking too long to complete
or the server has failed. Please see the server log files for command
status. Please start with the --verbose option in order to
see early messages. Command start-domain failed.
There was a stop-domain failure in glassfish CI some time
back which was fixed by correcting the docker image.
Regards,
Alwin
On 11/06/20 10:52 pm, arjan tijms wrote:
Hi,
I just noticed an old issue with the CI has
resurfaced.
Seemingly randomly, GlassFish will fail to
start up:
12:11:19 ===== TEST RUN - STARTING GLASSFISH
AND DB =====
12:21:20 Waiting for domain1 to start
.......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
12:21:20 No response from the Domain
Administration Server (domain1) after 600
seconds.
12:21:20 The command is either taking too
long to complete or the server has failed.
12:21:20 Please see the server log files for
command status.
12:21:20 Please start with the --verbose
option in order to see early messages.
Repeating the script (within the same test run)
never helps. This is automatically done during
the test. However the exact same build does start
up on other nodes.