Bug 2172633

Summary:	galara: FTBFS in Fedora rawhide/f39
Product:	[Fedora] Fedora	Reporter:	Thomas Rodgers <trodgers>
Component:	galera	Assignee:	Michal Schorm <mschorm>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	damien.ciabrini, fdinitto, hhorak, ljavorsk, mbayer, mschorm, zmiklank
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-02-28 18:06:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Thomas Rodgers 2023-02-22 20:02:55 UTC

https://koji.fedoraproject.org/koji/buildinfo?buildID=2156312

This may be a spurious test failure on ppc64le, test log was -

+ /usr/bin/ctest --test-dir redhat-linux-build --output-on-failure --force-new-ctest-process -j8
Internal ctest changing into directory: /builddir/build/BUILD/galera-26.4.13/redhat-linux-build
Test project /builddir/build/BUILD/galera-26.4.13/redhat-linux-build
    Start 1: gu_tests
    Start 2: gu_tests++
    Start 3: check_gcomm
    Start 4: gcache_tests
    Start 5: gcs_tests
    Start 6: galera_check
    Start 7: wsrep_test
1/7 Test #7: wsrep_test .......................   Passed    0.33 sec
2/7 Test #4: gcache_tests .....................   Passed    1.09 sec
3/7 Test #3: check_gcomm ......................   Passed    2.34 sec
4/7 Test #2: gu_tests++ .......................   Passed    3.56 sec
5/7 Test #1: gu_tests .........................   Passed    3.63 sec
6/7 Test #6: galera_check .....................   Passed   14.10 sec
7/7 Test #5: gcs_tests ........................***Failed   22.50 sec
Running suite(s): GCS component message
100%: Checks: 1, Failures: 0, Errors: 0
Running suite(s): GCS send monitor
100%: Checks: 5, Failures: 0, Errors: 0
Running suite(s): GCS state message
100%: Checks: 7, Failures: 0, Errors: 0
Running suite(s): GCS FIFO functions
100%: Checks: 1, Failures: 0, Errors: 0
Running suite(s): GCS core protocol
100%: Checks: 1, Failures: 0, Errors: 0
Running suite(s): GCS defragmenter
100%: Checks: 2, Failures: 0, Errors: 0
Running suite(s): GCS node context
100%: Checks: 1, Failures: 0, Errors: 0
Running suite(s): GCS membership changes
75%: Checks: 4, Failures: 0, Errors: 1
/builddir/build/BUILD/galera-26.4.13/gcs/src/unit_tests/gcs_memb_test.cpp:30:E:gcs_memb:gcs_memb_test_465E:0: (after this point) Test timeout expired
Running suite(s): CC functions
100%: Checks: 2, Failures: 0, Errors: 0
Running suite(s): GCS group context
100%: Checks: 5, Failures: 0, Errors: 0
Running suite(s): GCS backend interface
100%: Checks: 1, Failures: 0, Errors: 0
Running suite(s): GCS core context
100%: Checks: 6, Failures: 0, Errors: 0
Running suite(s): GCS state transfer FC
100%: Checks: 3, Failures: 0, Errors: 0
Total test failed: 1
86% tests passed, 1 tests failed out of 7
Total Test time (real) =  22.51 sec
The following tests FAILED:
	  5 - gcs_tests (Failed)
Errors while running CTest

Comment 1 Thomas Rodgers 2023-02-23 07:21:55 UTC

I tried to re-run the build to see if the ppc64le failure was transient. It would seem that is not the case -

https://koji.fedoraproject.org/koji/taskinfo?taskID=97886619

Comment 2 Lukas Javorsky 2023-02-28 09:07:43 UTC

No failure on my build: https://koji.fedoraproject.org/koji/taskinfo?taskID=98064388

Did you build it from the rawhide branch, or did you change anything within the package?

Comment 3 Thomas Rodgers 2023-02-28 18:06:49 UTC

(In reply to Lukas Javorsky from comment #2)
> No failure on my build:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=98064388
> 
> Did you build it from the rawhide branch, or did you change anything within
> the package?

Not a Proven Packager, so I can't make any changes to the package.

I still think it was a transient failure on that architecture, it seems to be resolved now, closing this issue.