Eric Shu created GEODE-9442:
-------------------------------
Summary: CI Failure: acceptance-test-openjdk8 timed out
Key: GEODE-9442
URL: https://issues.apache.org/jira/browse/GEODE-9442
Project: Geode
Issue Type: Bug
Components: redis
Reporter: Eric Shu
This acceptance-test-openjdk8 failed due to timeout.
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/88
It does not appear to be one particular test hang -- as all running tests are
finished showing status of SUCCESS.
However, it shows that gradle no able to shut down one test worker:
in daemon-4088.out.log under .gradle_logs directory following exception was
seen:
Daemon is stopping immediately stop command received
Daemon vm is shutting down... The daemon has exited normally or was terminated
in response to a user interrupt.
failed to abort Gradle Test Executor 143
org.gradle.process.internal.ExecException: A problem occurred waiting for
process 'Gradle Test Executor 143' to complete.
at
org.gradle.process.internal.DefaultExecHandle.execExceptionFor(DefaultExecHandle.java:241)
at
org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:218)
at
org.gradle.process.internal.DefaultExecHandle.failed(DefaultExecHandle.java:369)
at
org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:87)
at
org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42)
at
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
at
org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: Shutdown in progress
at
java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82)
at java.lang.Runtime.removeShutdownHook(Runtime.java:239)
at
org.gradle.process.internal.shutdown.ShutdownHooks.removeShutdownHook(ShutdownHooks.java:33)
at
org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:208)
at
org.gradle.process.internal.DefaultExecHandle.aborted(DefaultExecHandle.java:365)
at
org.gradle.process.internal.ExecHandleRunner.completed(ExecHandleRunner.java:108)
at
org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:84)
... 7 more
Also, in
geode-apis-compatible-with-redis/build/test-results/acceptanceTest/binary
output.bin file that Redis container was started but no further information for
its shutdown. No sure if this is normal or not.
^A<9c>^H^@<8a>^A[info 2021/07/20 16:55:00.011 UTC <Test worker> tid=0xa] Ryuk
started - will monitor and terminate Testcontainers containers on JVM exit
^A<9c>^H^@^A
^A<9c>^H^@Q[info 2021/07/20 16:55:00.012 UTC <Test worker> tid=0xa] Checking
the system...
^A<9c>^H^@^A
^A<9c>^H^@p[info 2021/07/20 16:55:00.013 UTC <Test worker> tid=0xa]
â<9c><94>ï¸<8e> Docker server version should be at least 1.6.0
^A<9c>^H^@^A
^A<9c>^H^@~[info 2021/07/20 16:55:00.142 UTC <Test worker> tid=0xa]
â<9c><94>ï¸<8e> Docker environment should have more than 2GB free disk space
^A<9c>^H^@^A
^A<9c>^H^@d[info 2021/07/20 16:55:00.161 UTC <Test worker> tid=0xa] Creating
container for image: redis:5.0.6
^A<9c>^H^@^A
^A<9c>^H^@<97>^A[info 2021/07/20 16:55:00.218 UTC <Test worker> tid=0xa]
Starting container with ID:
3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634
^A<9c>^H^@^A
^A<9c>^H^@<9e>^A[info 2021/07/20 16:55:00.658 UTC <Test worker> tid=0xa]
Container redis:5.0.6 is starting:
3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634
^A<9c>^H^@^A
^A<9c>^H^@d[info 2021/07/20 16:55:00.789 UTC <Test worker> tid=0xa] Container
redis:5.0.6 started in PT0.644S
^A<9c>^H^@^A
^A<9c>^H^@r[info 2021/07/20 16:55:00.791 UTC <Test worker> tid=0xa] Started
redis container with exposed port 6379 -> 33290
Someone has more knowledge of redis container should take a look and determine
if it is an real issue or not.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
