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

Mikhail Gryzykhin commented on BEAM-5116:
-----------------------------------------

Synced with Luke if he had ideas out of head.

We can look into enabling core dump on build failure and go further from there.

I'm reducing priority on this issue, until it repeats itself.

> beam_PostCommit_Java_GradleBuild 
> :beam-runners-google-cloud-dataflow-java:examplesJavaIntegrationTest Failed 
> build. System failure.
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: BEAM-5116
>                 URL: https://issues.apache.org/jira/browse/BEAM-5116
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system, test-failures
>            Reporter: Mikhail Gryzykhin
>            Priority: Major
>
> [https://builds.apache.org/view/A-D/view/Beam/job/beam_PostCommit_Java_GradleBuild/1214/]
> Find log subset below. Suspect is fail is due to memory limitations or zip 
> source availability/integrity.
> > Task :beam-runners-google-cloud-dataflow-java:examplesJavaIntegrationTest 
> > FAILED
> Build cache key for task 
> ':beam-runners-google-cloud-dataflow-java:examplesJavaIntegrationTest' is 
> 12c45ad8abd6cf3734c37d0c2592d429
> Task ':beam-runners-google-cloud-dataflow-java:examplesJavaIntegrationTest' 
> is not up-to-date because:
>   No history is available.
> Starting process 'Gradle Test Executor 129'. Working directory: 
> /home/jenkins/jenkins-slave/workspace/beam_PostCommit_Java_GradleBuild/src/runners/google-cloud-dataflow-java
>  Command: /usr/local/asfpackages/java/jdk1.8.0_172/bin/java 
> -DbeamTestPipelineOptions=["--runner=TestDataflowRunner","--project=apache-beam-testing","--tempRoot=gs://temp-storage-for-end-to-end-tests"]
>  
> -Djava.security.manager=worker.org.gradle.process.internal.worker.child.BootstrapSecurityManager
>  -Dorg.gradle.native=false -Dfile.encoding=UTF-8 -Duser.country=US 
> -Duser.language=en -Duser.variant -ea -cp 
> /home/jenkins/.gradle/caches/4.8/workerMain/gradle-worker.jar 
> worker.org.gradle.process.internal.worker.GradleWorkerMain 'Gradle Test 
> Executor 129'
> Successfully started process 'Gradle Test Executor 129'
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGBUS (0x7) at pc=0x00007fc14674a4e2, pid=7054, tid=0x00007fc0c1150700
> #
> # JRE version: Java(TM) SE Runtime Environment (8.0_172-b11) (build 
> 1.8.0_172-b11)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.172-b11 mixed mode 
> linux-amd64 compressed oops)
> # Problematic frame:
> # C  [libzip.so+0x124e2]  newEntry+0x62
> #
> # Failed to write core dump. Core dumps have been disabled. To enable core 
> dumping, try "ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> # 
> /home/jenkins/jenkins-slave/workspace/beam_PostCommit_Java_GradleBuild/src/runners/google-cloud-dataflow-java/hs_err_pid7054.log
> Compiled method (nm)    1382  211     n 0       
> java.util.zip.ZipFile::getEntry (native)
>  total in heap  [0x00007fc1313495d0,0x00007fc131349940] = 880
>  relocation     [0x00007fc1313496f8,0x00007fc131349740] = 72
>  main code      [0x00007fc131349740,0x00007fc131349940] = 512
> #
> # If you would like to submit a bug report, please visit:
> #   
> [http://bugreport.java.com/bugreport/crash.jsp]
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to