Bug 991712

Also can be reproduced by re-building junitperf on arm, see bug 993919 for build.log example.

*** Bug 993919 has been marked as a duplicate of this bug. ***

How critical is this, by the way? Chris is on vacation until end of next week (except for a couple of days) so it might be until after then before this is addressed.

Well, the work around seems to be, 'keep resubmitting the build until koji randomly picks a non-arm builder' but because there are quite a high percentage of arm builders now, this happens quite often.

It would be very useful if you could attach the hs_error.log [ /tmp/jvm-14411/hs_error.log  in the above example ] to this bug.

Created attachment 785171 [details]
junitperf koji scratch build.log

Please see attached build.log that contains the contents of the hs_error.log from a koji scratch build.

If you don't have any ARM hardware to hand, you can test or reproduce this and view the hs_error.log by applying the following patch to the junitperf package, for example, and then issuing a scratch build in koji:

http://fpaste.org/31228/40741137/

fedpkg srpm && koji build --scratch f20 `pwd`/junitperf-1.9.1-12.fc20.src.rpm

Looking at the stack trace I suspect this is a problem with the backport of 
cpu  20130618  bug  8001330. I'll be away for 1 week canoeing... will look at this after I return. Need to reexamine the backport of 8001330 to hsx23.

Created attachment 785215 [details]
5803100: grizzly koji scratch build.log with hs_error.log

This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Created attachment 807831 [details]
F21 grizzly koji scratch build.log with hs_error.log

also in f21/rawhide
regards

Created attachment 807832 [details]
F21 grizzly koji scratch build.log

I'm also receiving this error: 

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (os_linux_zero.cpp:285), pid=3282, tid=3052991584
#  fatal error: caught unhandled signal 7
#
# JRE version: 7.0_25-b33
# Java VM: OpenJDK Zero VM (23.25-b01 mixed mode linux-arm )
# 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:
# /tmp/jvm-3282/hs_error.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
#   http://icedtea.classpath.org/bugzilla
#

seem affected also java8

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (os_linux_zero.cpp:202), pid=29988, tid=3061556320
#  Error: ShouldNotCall()
#
# JRE version: OpenJDK Runtime Environment (8.0_05-b13) (build 1.8.0_05-b13)
# Java VM: OpenJDK Zero VM (25.5-b02 interpreted mode linux-arm )
# 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:
# /builddir/build/BUILD/kryo-2.22/hs_err_pid29988.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
#
/bin/sh: line 1: 29988 Aborted                 /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5/jre/bin/java -jar /builddir/build/BUILD/kryo-2.22/target/surefire/surefirebooter2898180989974157080.jar /builddir/build/BUILD/kryo-2.22/target/surefire/surefire2357075615981149990tmp /builddir/build/BUILD/kryo-2.22/target/surefire/surefire_05021321386840445219tmp

Hi If you can provide an isolated testcase that reproduces this it will expedite a fix. Also is the hs_err log [ /builddir/build/BUILD/kryo-2.22/hs_err_pid29988.log ] somewhere I can reference?

Thx.

Created attachment 907320 [details]
F21 kryo 2.22 hs_err_pid.log

sorry for delay

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.