[ 
https://issues.apache.org/jira/browse/FLINK-30844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682686#comment-17682686
 ] 

Anton Kalashnikov commented on FLINK-30844:
-------------------------------------------

I don't see a problem here.  I just see that the thread is finishing longer 
than 50ms but I see it isn't stuck and make progress which is good. Normally, 
it should take about 1ms but 50ms  is also not something extraordinal on the 
overloaded machine. The only thing is a synchronization inside the finishing 
loop which can delay the actual finish but I have no evidence that it is a 
reason. 
I will try to check more ideas but if nothing works I will just increase the 
waiting interval for this test.(I actually think that 50ms is low anyway)

> TaskTest.testInterruptibleSharedLockInInvokeAndCancel causes a JVM shutdown 
> with exit code 239
> ----------------------------------------------------------------------------------------------
>
>                 Key: FLINK-30844
>                 URL: https://issues.apache.org/jira/browse/FLINK-30844
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination, Runtime / Task
>    Affects Versions: 1.17.0
>            Reporter: Matthias Pohl
>            Priority: Blocker
>              Labels: test-stability
>
> We're experiencing a fatal crash in {{TaskTest}}:
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=45440&view=logs&j=0da23115-68bb-5dcd-192c-bd4c8adebde1&t=24c3384f-1bcb-57b3-224f-51bf973bbee8&l=8334
> {code}
> [...]
> Jan 31 01:03:12 [ERROR] Process Exit Code: 239
> Jan 31 01:03:12 [ERROR] Crashed tests:
> Jan 31 01:03:12 [ERROR] org.apache.flink.runtime.taskmanager.TaskTest
> Jan 31 01:03:12 [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:748)
> Jan 31 01:03:12 [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.access$700(ForkStarter.java:121)
> Jan 31 01:03:12 [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter$1.call(ForkStarter.java:393)
> Jan 31 01:03:12 [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter$1.call(ForkStarter.java:370)
> Jan 31 01:03:12 [ERROR] at 
> java.util.concurrent.FutureTask.run(FutureTask.java:266)
> Jan 31 01:03:12 [ERROR] at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> Jan 31 01:03:12 [ERROR] at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> Jan 31 01:03:12 [ERROR] at java.lang.Thread.run(Thread.java:748)
> Jan 31 01:03:12 [ERROR] -> [Help 1]
> Jan 31 01:03:12 [ERROR] 
> Jan 31 01:03:12 [ERROR] To see the full stack trace of the errors, re-run 
> Maven with the -e switch.
> Jan 31 01:03:12 [ERROR] Re-run Maven using the -X switch to enable full debug 
> logging.
> Jan 31 01:03:12 [ERROR] 
> Jan 31 01:03:12 [ERROR] For more information about the errors and possible 
> solutions, please read the following articles:
> Jan 31 01:03:12 [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> Jan 31 01:03:12 [ERROR] 
> Jan 31 01:03:12 [ERROR] After correcting the problems, you can resume the 
> build with the command
> Jan 31 01:03:12 [ERROR]   mvn <goals> -rf :flink-runtime
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to