Test failure for :x-pack:qa:rolling-upgrade-multi-cluster:v6.8.11#follower#oneThirdUpgradedTest #57969
Description
Not sure whether this is a transient issue when setting up the test infrastructure. But it started to occur from Jun 01 and has happened 4 times so far. The node seems crashed in the setup phase and the tests did not even get a chance to run. Looking into the logs, I noticed the following error:
» 2020-06-11 05:43:24,913349 UTC [543325] ERROR CNamedPipeFactory.cc@226 Unable to open named pipe /dev/shm/elastic+elasticsearch+7.x+matrix-java-periodic/ES_RUNTIME_JAVA/zulu8/nodes/general-purpose/x-pack/qa/rolling-upgrade-multi-cluster/build/testclusters/v6.8.1-follower-0/tmp/controller_log_542785 for writing: Interrupted system call » 2020-06-11 05:43:24,913435 UTC [543325] ERROR CLogger.cc@298 Cannot log to named pipe /dev/shm/elastic+elasticsearch+7.x+matrix-java-periodic/ES_RUNTIME_JAVA/zulu8/nodes/general-purpose/x-pack/qa/rolling-upgrade-multi-cluster/build/testclusters/v6.8.1-follower-0/tmp/controller_log_542785 as it could not be opened for writing » 2020-06-11 05:43:24,913445 UTC [543325] FATAL Main.cc@102 Could not reconfigure logging The C++ code suggests it to be ML related? I am labelling this as ml so experts of this area can get a closer look.
Build scan:
- https://gradle-enterprise.elastic.co/s/hcrqg2n333qeu
- https://gradle-enterprise.elastic.co/s/u5pzxtcecn6h2
- https://gradle-enterprise.elastic.co/s/fd64ycjtlfssw
- https://gradle-enterprise.elastic.co/s/bbvp73rfgiuq4
Repro line:
There is no reproduction line since the tests didn't run. But I tried with
./gradlew ':x-pack:qa:rolling-upgrade-multi-cluster:v6.8.11#follower#oneThirdUpgradedTest' -Dtests.security.manager=true -Druntime.java=8
locally and it did not reproduce.
Reproduces locally?:
See above.
Applicable branches:
7.x
Failure history:
See build scan section.
Failure excerpt:
process was found dead while waiting for ports files, node{:x-pack:qa:rolling-upgrade-multi-cluster:v6.8.1-leader-2}