Description of problem: Two tests are failing on s390x architecture. Version-Release number of selected component (if applicable): 1.5.1 How reproducible: Always Steps to Reproduce: 1. Download release curl -L https://github.com/cgreen-devs/cgreen/archive/1.5.1/cgreen-1.5.1.tar.gz -o cgreen-1.5.1.tar.gz 2. Install dependencies sudo dnf install cmake gcc-c++ binutils-devel 3. Build Cgreen tar zxf cgreen-1.5.1.tar.gz && cd cgreen-1.5.1 cmake . make 4. Run tests ctest Actual results: Test project /home/yoyo/cgreen-1.5.1 Start 1: test_cgreen_c 1/30 Test #1: test_cgreen_c ...................................................... Passed 4.42 sec Start 2: test_cgreen_c_run_named_test 2/30 Test #2: test_cgreen_c_run_named_test ....................................... Passed 0.10 sec Start 3: runner_test_cgreen_c 3/30 Test #3: runner_test_cgreen_c ...............................................***Failed 12.39 sec Start 4: test_cgreen_cpp 4/30 Test #4: test_cgreen_cpp .................................................... Passed 4.52 sec Start 5: test_cgreen_cpp_run_named_test 5/30 Test #5: test_cgreen_cpp_run_named_test ..................................... Passed 0.12 sec Start 6: runner_test_cgreen_cpp 6/30 Test #6: runner_test_cgreen_cpp .............................................***Failed 15.74 sec Start 7: constraint_messsages 7/30 Test #7: constraint_messsages ............................................... Passed 1.87 sec Start 8: custom_constraint_messsages 8/30 Test #8: custom_constraint_messsages ........................................ Passed 1.31 sec Start 9: mock_messsages 9/30 Test #9: mock_messsages ..................................................... Passed 1.98 sec Start 10: failure_messages 10/30 Test #10: failure_messages ................................................... Passed 4.40 sec Start 11: assertion_messages 11/30 Test #11: assertion_messages ................................................. Passed 1.36 sec Start 12: ignore_messages 12/30 Test #12: ignore_messages .................................................... Passed 1.39 sec Start 13: xml_output 13/30 Test #13: xml_output ......................................................... Passed 1.50 sec Start 14: cgreen_runner_unit_tests 14/30 Test #14: cgreen_runner_unit_tests ........................................... Passed 0.46 sec Start 15: cgreen_runner_usage 15/30 Test #15: cgreen_runner_usage ................................................ Passed 0.16 sec Start 16: cgreen_runner_quiet 16/30 Test #16: cgreen_runner_quiet ................................................ Passed 0.40 sec Start 17: cgreen_runner_suite_name 17/30 Test #17: cgreen_runner_suite_name ........................................... Passed 0.44 sec Start 18: cgreen_runner_fail_on_non_existing_library 18/30 Test #18: cgreen_runner_fail_on_non_existing_library ......................... Passed 0.17 sec Start 19: cgreen_runner_fail_on_non_existing_library_with_suite 19/30 Test #19: cgreen_runner_fail_on_non_existing_library_with_suite .............. Passed 0.20 sec Start 20: cgreen_runner_verbose 20/30 Test #20: cgreen_runner_verbose .............................................. Passed 0.47 sec Start 21: cgreen_runner_version 21/30 Test #21: cgreen_runner_version .............................................. Passed 0.17 sec Start 22: cgreen_runner_single_explicit_named_test 22/30 Test #22: cgreen_runner_single_explicit_named_test ........................... Passed 0.23 sec Start 23: cgreen_runner_patternmatched_testnames 23/30 Test #23: cgreen_runner_patternmatched_testnames ............................. Passed 0.50 sec Start 24: cgreen_runner_patternmatched_testnames_in_patternmatched_context 24/30 Test #24: cgreen_runner_patternmatched_testnames_in_patternmatched_context ... Passed 0.49 sec Start 25: cgreen_runner_wildcarded_tests_in_named_context 25/30 Test #25: cgreen_runner_wildcarded_tests_in_named_context .................... Passed 0.52 sec Start 26: cgreen_runner_wildcarded_tests_in_wildcarded_context 26/30 Test #26: cgreen_runner_wildcarded_tests_in_wildcarded_context ............... Passed 0.45 sec Start 27: cgreen_runner_with_xml_reporter 27/30 Test #27: cgreen_runner_with_xml_reporter .................................... Passed 0.59 sec Start 28: cgreen_runner_multiple_libraries 28/30 Test #28: cgreen_runner_multiple_libraries ................................... Passed 1.21 sec Start 29: discoverer_acceptance_tests 29/30 Test #29: discoverer_acceptance_tests ........................................ Passed 0.47 sec Start 30: discoverer_unit_tests 30/30 Test #30: discoverer_unit_tests .............................................. Passed 0.59 sec 93% tests passed, 2 tests failed out of 30 Total Test time (real) = 59.39 sec The following tests FAILED: 3 - runner_test_cgreen_c (Failed) 6 - runner_test_cgreen_cpp (Failed) Errors while running CTest Output from these tests are in: /home/yoyo/cgreen-1.5.1/Testing/Temporary/LastTest.log Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely. Expected results: All tests finished successfully.
https://github.com/cgreen-devs/cgreen/commit/d38ff73eaebd7a0baf76c6a0645d9adbb2db28a5 is the first commit where the 2 tests start to fail
unfortunately there are no details printed what or why is failing, I recommend opening an issue upstream
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.