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

Matthias Pohl commented on FLINK-30540:
---------------------------------------

It's caused by a segmentation fault:
{code}
Jan 01 00:56:39 [INFO] #
Jan 01 00:56:39 [INFO] # A fatal error has been detected by the Java Runtime 
Environment:
Jan 01 00:56:39 [INFO] #
Jan 01 00:56:39 [INFO] #  SIGSEGV (0xb) at pc=0x00007f8168722f67, pid=771, 
tid=0x00007f7fbcc2c700
Jan 01 00:56:39 [INFO] #
Jan 01 00:56:39 [INFO] # JRE version: OpenJDK Runtime Environment (8.0_292-b10) 
(build 1.8.0_292-8u292-b10-0ubuntu1~16.04.1-b10)
Jan 01 00:56:39 [INFO] # Java VM: OpenJDK 64-Bit Server VM (25.292-b10 mixed 
mode linux-amd64 compressed oops)
Jan 01 00:56:39 [INFO] # Problematic frame:
{code}
A core dump was provided.

> DataSinkTaskTest failed with a 143 exit code
> --------------------------------------------
>
>                 Key: FLINK-30540
>                 URL: https://issues.apache.org/jira/browse/FLINK-30540
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Task, Tests
>    Affects Versions: 1.17.0
>            Reporter: Matthias Pohl
>            Priority: Critical
>              Labels: test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=44366&view=logs&j=a549b384-c55a-52c0-c451-00e0477ab6db&t=eef5922c-08d9-5ba3-7299-8393476594e7&l=8480
> We experienced a 143 exit code when finalizing {{DataSinkTaskTest}}:
> {code}
> Jan 01 00:58:47 [ERROR] at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> Jan 01 00:58:47 [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> Jan 01 00:58:47 [ERROR] at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> Jan 01 00:58:47 [ERROR] at 
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> Jan 01 00:58:47 [ERROR] at 
> org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> Jan 01 00:58:47 [ERROR] at 
> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> Jan 01 00:58:47 [ERROR] at 
> org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> Jan 01 00:58:47 [ERROR] at 
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Jan 01 00:58:47 [ERROR] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> Jan 01 00:58:47 [ERROR] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Jan 01 00:58:47 [ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
> Jan 01 00:58:47 [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> Jan 01 00:58:47 [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> Jan 01 00:58:47 [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> Jan 01 00:58:47 [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Jan 01 00:58:47 [ERROR] Caused by: 
> org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM 
> terminated without properly saying goodbye. VM crash or System.exit called?
> Jan 01 00:58:47 [ERROR] Command was /bin/sh -c cd /__w/3/s/flink-runtime && 
> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -XX:+UseG1GC -Xms256m -Xmx768m 
> -jar 
> /__w/3/s/flink-runtime/target/surefire/surefirebooter7079560860955914030.jar 
> /__w/3/s/flink-runtime/target/surefire 2023-01-01T00-54-17_721-jvmRun4 
> surefire118217553075734742tmp surefire_1430697542098749596tmp
> Jan 01 00:58:47 [ERROR] Error occurred in starting fork, check output in log
> Jan 01 00:58:47 [ERROR] Process Exit Code: 134
> Jan 01 00:58:47 [ERROR] Crashed tests:
> Jan 01 00:58:47 [ERROR] org.apache.flink.runtime.operators.DataSinkTaskTest
> Jan 01 00:58:47 [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:748)
> Jan 01 00:58:47 [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.access$700(ForkStarter.java:121)
> Jan 01 00:58:47 [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter$1.call(ForkStarter.java:393)
> Jan 01 00:58:47 [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter$1.call(ForkStarter.java:370)
> Jan 01 00:58:47 [ERROR] at 
> java.util.concurrent.FutureTask.run(FutureTask.java:266)
> Jan 01 00:58:47 [ERROR] at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> Jan 01 00:58:47 [ERROR] at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> Jan 01 00:58:47 [ERROR] at java.lang.Thread.run(Thread.java:748)
> Jan 01 00:58:47 [ERROR] -> [Help 1]
> Jan 01 00:58:47 [ERROR] 
> Jan 01 00:58:47 [ERROR] To see the full stack trace of the errors, re-run 
> Maven with the -e switch.
> Jan 01 00:58:47 [ERROR] Re-run Maven using the -X switch to enable full debug 
> logging.
> Jan 01 00:58:47 [ERROR] 
> Jan 01 00:58:47 [ERROR] For more information about the errors and possible 
> solutions, please read the following articles:
> Jan 01 00:58:47 [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}



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

Reply via email to