Bug 1859925 - jacop-test failed on ppc64le
Summary: jacop-test failed on ppc64le
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: java-11-openjdk
Version: 33
Hardware: ppc64le
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: jiri vanek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1858054
TreeView+ depends on / blocked
 
Reported: 2020-07-23 10:28 UTC by Antonio T. sagitter
Modified: 2021-11-30 16:21 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-11-30 16:21:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
mp's jacop-test log (102.46 KB, text/plain)
2020-07-23 10:28 UTC, Antonio T. sagitter
no flags Details

Description Antonio T. sagitter 2020-07-23 10:28:53 UTC
Created attachment 1702212 [details]
mp's jacop-test log

Created attachment 1702212 [details]
mp's jacop-test log

Description of problem:
mp's jacop-test is failing on PPC64le only with `java-11-openjdk ppc64le-1:11.0.8.10-0.fc33`

Version-Release number of selected component (if applicable):
1:11.0.8.10-0

How reproducible:
Build mp-3.1.0-28.20200303git7fd4828 on f33-java11

Actual results:
See attached log.
See https://koji.fedoraproject.org/koji/taskinfo?taskID=47681464

Expected results:
No error.

Comment 1 jiri vanek 2020-07-23 10:49:25 UTC
Can you please extract a single reprodcuer?

Comment 2 jiri vanek 2020-07-23 10:52:59 UTC
This build https://koji.fedoraproject.org/koji/buildinfo?buildID=1543339 was also done by 1:11.0.8.10-0.fc33 and is passed.
I guess the build platform matters as you write. Does it sigsev 100%?

Comment 3 Antonio T. sagitter 2020-07-23 17:31:39 UTC
(In reply to jiri vanek from comment #1)
> Can you please extract a single reprodcuer?

??

Comment 4 jiri vanek 2020-07-23 20:08:32 UTC
Having isolated reporducer will speed the fix quite a lot.
As it is ppc64le only, it will be quite hard to reproduce and fix.
I'm currently working on inclusion of jacop to downstream integration tests, whcih run on ppc64le. Before it is done, I will not have verified failure, not having better reprodcuer.

Comment 5 Severin Gehwolf 2020-07-24 08:48:45 UTC
I've tried to reproduce this on a ppc64-le machine. "fedpkg mockbuild" fails with:

-- Build files have been written to: /builddir/build/BUILD/mp-7fd4828c934fccf7367499c9e01cc9a1e90a2093/build/ppc64le-redhat-linux-gnu
+ /usr/bin/make -O -j4 V=1 VERBOSE=1
make: *** No targets specified and no makefile found.  Stop.
error: Bad exit status from /var/tmp/rpm-tmp.MnI4Fw (%build)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.MnI4Fw (%build)
Finish: rpmbuild mp-3.1.0-28.20200303git7fd4828.fc33.src.rpm
Finish: build phase for mp-3.1.0-28.20200303git7fd4828.fc33.src.rpm
ERROR: Exception(/home/fedora/jerboaa/mp/mp-3.1.0-28.20200303git7fd4828.fc33.src.rpm) Config(fedora-rawhide-ppc64le) 1 minutes 51 second

This isn't the expected failure :(

Comment 6 Severin Gehwolf 2020-07-24 08:50:48 UTC
ppc64le-test.fedorainfracloud.org is the machine I've used, fwiw.

Comment 7 Antonio T. sagitter 2020-07-24 09:07:11 UTC
(In reply to Severin Gehwolf from comment #5)
> I've tried to reproduce this on a ppc64-le machine. "fedpkg mockbuild" fails
> with:
> 
> -- Build files have been written to:
> /builddir/build/BUILD/mp-7fd4828c934fccf7367499c9e01cc9a1e90a2093/build/
> ppc64le-redhat-linux-gnu
> + /usr/bin/make -O -j4 V=1 VERBOSE=1
> make: *** No targets specified and no makefile found.  Stop.
> error: Bad exit status from /var/tmp/rpm-tmp.MnI4Fw (%build)
> 
> 
> RPM build errors:
>     Bad exit status from /var/tmp/rpm-tmp.MnI4Fw (%build)
> Finish: rpmbuild mp-3.1.0-28.20200303git7fd4828.fc33.src.rpm
> Finish: build phase for mp-3.1.0-28.20200303git7fd4828.fc33.src.rpm
> ERROR:
> Exception(/home/fedora/jerboaa/mp/mp-3.1.0-28.20200303git7fd4828.fc33.src.
> rpm) Config(fedora-rawhide-ppc64le) 1 minutes 51 second
> 
> This isn't the expected failure :(

It's due to a recent change of CMake.
Please, use this srpm:
https://kojipkgs.fedoraproject.org//work/tasks/2181/47742181/mp-3.1.0-29.20200303git7fd4828.fc33.src.rpm

Comment 8 Ben Cotton 2020-08-11 13:49:17 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 9 jiri vanek 2020-08-12 08:35:26 UTC
Hi!

I had finally run repeated mvn clean install test on ppc64le on f32, centos7 and centos8. I have not reproduced.  I currently do not have f33 in pool, but will have soon. So this remain f33 specific.

Comment 10 Ben Cotton 2021-11-04 17:34:43 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 '33'.

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 33 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.

Comment 11 Ben Cotton 2021-11-30 16:21:01 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.


Note You need to log in before you can comment on or make changes to this bug.