fix: ensure that onStopLeading is called #4893
Triggered via pull request
September 19, 2023 10:23
Status
Success
Total duration
35m 57s
Artifacts
–
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
Annotations
4 errors
Java 11 Maven
Task io.fabric8.kubernetes.client.utils.internal.SerialExecutor$$Lambda$681/0x00000001005f4c40@7e195901 rejected from java.util.concurrent.ThreadPoolExecutor@70dea8b2[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 0]
|
Java 11 Maven
Task io.fabric8.kubernetes.client.utils.internal.SerialExecutor$$Lambda$681/0x00000001005f4c40@7d6ad8ee rejected from java.util.concurrent.ThreadPoolExecutor@73ad3933[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 0]
|
Java 11 Maven
Task io.fabric8.kubernetes.client.utils.internal.SerialExecutor$$Lambda$681/0x00000001005f4c40@1ec6caad rejected from java.util.concurrent.ThreadPoolExecutor@10012705[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 0]
|
Java 11 Maven
Task io.fabric8.kubernetes.client.utils.internal.SerialExecutor$$Lambda$681/0x00000001005f4c40@38f6859b rejected from java.util.concurrent.ThreadPoolExecutor@36317cf5[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 0]
|