Bug 1856769 - mpich-3.3.2-5.fc33 FTBFS: test_primitives test fails on ppc64le
Summary: mpich-3.3.2-5.fc33 FTBFS: test_primitives test fails on ppc64le
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mpich
Version: rawhide
Hardware: ppc64le
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zbigniew Jędrzejewski-Szmek
QA Contact: Fedora Extras Quality Assurance
URL: https://koschei.fedoraproject.org/pac...
Whiteboard:
Depends On:
Blocks: F33FTBFS
TreeView+ depends on / blocked
 
Reported: 2020-07-14 12:27 UTC by Petr Pisar
Modified: 2020-08-04 23:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-04 23:19:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Pisar 2020-07-14 12:27:57 UTC
mpich-3.3.2-5.fc33 fails to build in Fedora 33 on ppc64le, because a test fails there:

FAIL: test_primitives
=====================
[...]
Testing simple pointer load-linked/store-conditional functionality     PASSED
Testing integer LL/SC ABA with 2 threads                                  Unexpected success of OPA_SC_int
    Unexpected success of OPA_SC_int
    Unexpected success of OPA_SC_int
*FAILED*
        at test_primitives.c:4125 in test_threaded_llsc_int_aba()...
    False positives: 220 / 1001171
Testing pointer LL/SC ABA with 2 threads                                  Unexpected success of OPA_SC_ptr
    Unexpected success of OPA_SC_ptr
*FAILED*
        at test_primitives.c:4364 in test_threaded_llsc_ptr_aba()...
    False positives: 191 / 1000161
Testing integer load/store with 1 thread                               PASSED
[...]
***** 2 PRIMITIVES TESTS FAILED! *****
FAIL test_primitives (exit status: 1)

A difference between passing and failing build root is at <https://koschei.fedoraproject.org/build/8474383>.

Comment 1 Miro Hrončok 2020-08-04 23:19:33 UTC
The following builds were made after this report was opened: mpich-3.3.2-6.fc33


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