Fedora Account System
Red Hat Associate
Red Hat Customer
The check section fails on s390x after the latest change in the spec file, see bellow for details. from build.log ... Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.sQxFKB + umask 022 + cd /builddir/build/BUILD + cd java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x + for suffix in '""' ++ pwd + export JAVA_HOME=/builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image + JAVA_HOME=/builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image + md5sum /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/jre/lib/security/java.security 5ea976e209d0d0b5b6ab148416123e02 /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/jre/lib/security/java.security ++ md5sum /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/jre/lib/security/java.security ++ sed 's;\s.*;;' + currentMd5sum=5ea976e209d0d0b5b6ab148416123e02 + specfile=/builddir/build/SPECS/java-1.8.0-openjdk.spec + grep -e md5sum -A 20 /builddir/build/SPECS/java-1.8.0-openjdk.spec + grep 5ea976e209d0d0b5b6ab148416123e02 "${sum}" = '5ea976e209d0d0b5b6ab148416123e02' ]; then + /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/bin/javac -d . /builddir/build/SOURCES/TestCryptoLevel.java + /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/bin/java TestCryptoLevel Running with the unlimited policy. + /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/bin/javac -d . /builddir/build/SOURCES/TestECDSA.java ++ sed 's|\.java||' +++ basename /builddir/build/SOURCES/TestECDSA.java ++ echo TestECDSA.java + /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/bin/java TestECDSA Signature: 3045022100fa6afcde34b1bf35ad730f8079449e0813c5105226bdcbfda418784d8f7e506602203e11d0924e791de14bc8c6235c56aa8e9f9844301bed02423ce8055bdc0325e3 Test passed. + SERVER_JVM=/builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/jre/lib/s390x/server/libjvm.so + CLIENT_JVM=/builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/jre/lib/s390x/client/libjvm.so + ZERO_JVM=/builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/jre/lib/s390x/zero/libjvm.so + jvms=("$SERVER_JVM" "$CLIENT_JVM" "$ZERO_JVM") + for lib in '"${jvms[@]}"' + '[' -f /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/jre/lib/s390x/server/libjvm.so ']' + echo 'Testing /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/jre/lib/s390x/server/libjvm.so for debug symbols' Testing /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/jre/lib/s390x/server/libjvm.so for debug symbols + eu-readelf -S /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/jre/lib/s390x/server/libjvm.so + grep '] .debug_' [27] .debug_aranges PROGBITS 0000000000000000 0077283c 0001bf20 0 0 0 1 [28] .debug_info PROGBITS 0000000000000000 0078e75c 06ead1ab 0 0 0 1 [29] .debug_abbrev PROGBITS 0000000000000000 0763b907 001fed5b 0 0 0 1 [30] .debug_line PROGBITS 0000000000000000 0783a662 004b7ea5 0 0 0 1 [31] .debug_str PROGBITS 0000000000000000 07cf2507 0024c4ec 1 MS 0 0 1 [32] .debug_loc PROGBITS 0000000000000000 07f3e9f3 00e91f2e 0 0 0 1 [33] .debug_ranges PROGBITS 0000000000000000 08dd0921 004e2370 0 0 0 1 ++ wc --lines ++ egrep '\]\ .debug_(info|abbrev)' ++ eu-readelf -S /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/jre/lib/s390x/server/libjvm.so + test 2 == 2 + grep '00000000 0 FILE LOCAL DEFAULT ABS javaCalls.cpp' + eu-readelf -s /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/jre/lib/s390x/server/libjvm.so error: Bad exit status from /var/tmp/rpm-tmp.sQxFKB (%check) Bad exit status from /var/tmp/rpm-tmp.sQxFKB (%check) RPM build errors: Child return code was: 1 EXCEPTION: [Error()] Traceback (most recent call last): File "/usr/lib/python3.5/site-packages/mockbuild/trace_decorator.py", line 88, in trace result = func(*args, **kw) File "/usr/lib/python3.5/site-packages/mockbuild/util.py", line 562, in do raise exception.Error("Command failed. See logs for output.\n # %s" % (command,), child.returncode) mockbuild.exception.Error: Command failed. See logs for output. # bash --login -c /usr/bin/rpmbuild -bb --target s390x --nodeps /builddir/build/SPECS/java-1.8.0-openjdk.spec For full logs please see http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=2377694 Version-Release number of selected component (if applicable): java-1.8.0-openjdk-1.8.0.102-5.b14.fc26
Hi Omair, thats the changests of yours. Wil you take an look?
I think this is the cause - javaCalls.cpp at all in the readelf output <mock-chroot> sh-4.3# eu-readelf -s /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/build/jdk8.build/images/j2sdk-image/jre/lib/s390x/server/libjvm.so | grep javaCalls 592: 0000000000000000 0 FILE LOCAL DEFAULT ABS javaCalls.o I have the buildroot ready, do ping me for access to it.
(In reply to Dan Horák from comment #2) > I think this is the cause - javaCalls.cpp at all in the readelf output no javaCalls.cpp ...
(In reply to Dan Horák from comment #2) > <mock-chroot> sh-4.3# eu-readelf -s > /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.102-5.b14.fc26.s390x/openjdk/ > build/jdk8.build/images/j2sdk-image/jre/lib/s390x/server/libjvm.so | grep > javaCalls > 592: 0000000000000000 0 FILE LOCAL DEFAULT ABS javaCalls.o Can you still set a breakpoint in javaCalls.cpp when running this JVM? > I have the buildroot ready, do ping me for access to it. Could I get access to it, please?
(In reply to Omair Majid from comment #4) > Can you still set a breakpoint in javaCalls.cpp when running this JVM? To answer my own question: yes. I will relax that check to `egrep "javaCalls.(o|cpp)$"`.
Fxed with: http://pkgs.fedoraproject.org/cgit/rpms/java-1.8.0-openjdk.git/commit/?id=ea155293bfd4a813c4b3b5a0823a5fc055ece9d7 I did a build on s390 mockroot and it built fine with it.
Thanks, the build also succeeded in koji (http://s390.koji.fedoraproject.org/koji/buildinfo?buildID=436943)