Bug 2244926
| Summary: | mmlib: FTBFS in Fedora Rawhide | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sandro <gui1ty> |
| Component: | mmlib | Assignee: | Ben Beasley <code> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | code, neuro-sig |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| URL: | https://koschei.fedoraproject.org/package/mmlib | ||
| Whiteboard: | |||
| Fixed In Version: | mmlib-1.4.2-10.fc40 mmlib-1.4.2-7.el9 mmlib-1.4.2-8.fc38 mmlib-1.4.2-8.fc37 mmlib-1.4.2-8.el8 mmlib-1.4.2-10.fc39 mmlib-1.4.2-13.el10_0 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-10-19 17:19:12 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Sandro
2023-10-18 20:52:16 UTC
> Prime suspect appears to be the meson update from 1.0.1 to 1.2.1: https://koschei.fedoraproject.org/affected-by/meson?epoch1=0&version1=1.0.1&release1=1.fc38&epoch2=0&version2=1.2.1&release2=1.fc38&collection=f38
Prime suspect for `%meson_test -- --num-processes 1` no longer working, that is. I haven't got a clue about the test failure.
For the meson error, I found that
-%meson_test -- --num-processes 1
+%global _smp_build_ncpus 1
+%meson_test
works nicely.
-----
The failing test says:
▶ 5/5 - ../tests/socket-api-tests.c:socket:getaddrinfo_valid: Assertion 'rp->ai_socktype == exp_socktype' failed FAIL
▶ 5/5 - ../tests/socket-api-tests.c:socket:getaddrinfo_error: Assertion 'mm_get_lasterror_number() == 1010' failed: mm_get_lasterror_number() == 11, 1010 == 1010 FAIL
▶ 5/5 - ../tests/socket-api-tests.c:socket:create_invalid_sockclient: Assertion 'mm_create_sockclient("ssh://localhost:10") == -1' failed FAIL
A first guess was that that might be related to the offline build, but I see the same thing when I do a mock build with --enable-network.
Looking at F38 to winnow down the updated packages a bit, the first failing Koschei build is:
https://koschei.fedoraproject.org/build/16384749
It’s not immediately obvious what would be responsible.
This reproduces using meson directly in a git checkout, so I’ll report it upstream. Reported upstream in https://github.com/mmlabs-mindmaze/mmlib/issues/7 with detailed analysis. Partial fix offered in https://github.com/mmlabs-mindmaze/mmlib/pull/8; some discussion required for the third test failure, https://github.com/mmlabs-mindmaze/mmlib/issues/7#issuecomment-1770809321. Preparing to build a package with the meson fix, the PR for the first two failing tests, and the workaround for the third failing test. Currently working through and reporting/skipping additional architecture-dependent test failures. It’s amazing that this was building cleanly and then suddenly broke in multiple ways on all releases! I’m skipping the wait_signal test on ppc64le/aarch64 for https://github.com/mmlabs-mindmaze/mmlib/issues/9. I find that I still have occasional flaky timing-related failures on s390x: 4/5 internal tests OK 0.00s 1 subtests passed ▶ 5/5 - ../tests/file-api-tests.c:file:file_times: Assertion 'buf.atime == ts3.tv_sec' failed: buf.atime == 2147483647, ts3.tv_sec == 2239999890 FAIL ▶ 5/5 - ../tests/file-api-tests.c:file:file_times_now: Assertion 'buf.atime == ts3.tv_sec' failed: buf.atime == 2147483647, ts3.tv_sec == 2239999890 FAIL ▶ 5/5 - ../tests/file-api-tests.c:file:file_fd_times: Assertion 'buf.atime == ts3.tv_sec' failed: buf.atime == 2147483647, ts3.tv_sec == 2239999890 FAIL ▶ 5/5 - ../tests/file-api-tests.c:file:file_fd_times_now: Assertion 'buf.atime == ts3.tv_sec' failed: buf.atime == 2147483647, ts3.tv_sec == 2239999890 FAIL Plus I saw this once on ppc64le: ▶ 5/5 - ../tests/process-api-tests.c:process:spawn_error: Test timeout expired FAIL I’m not going to dig into any of those right now. I believe they’re all due to bad assumptions in the tests rather than real/serious problems. FEDORA-2023-77fb2cdaf1 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-77fb2cdaf1 FEDORA-2023-77fb2cdaf1 has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-aa62881cba has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-aa62881cba FEDORA-2023-aa62881cba has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-aa62881cba` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-aa62881cba See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-587b305c8a has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-587b305c8a FEDORA-2023-cae23d55ef has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-cae23d55ef FEDORA-EPEL-2023-c6137b5c66 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-c6137b5c66 FEDORA-EPEL-2023-e10308a01e has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-e10308a01e FEDORA-2023-587b305c8a has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-587b305c8a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-587b305c8a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-cae23d55ef has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-cae23d55ef` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-cae23d55ef See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2023-c6137b5c66 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-c6137b5c66 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2023-e10308a01e has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-e10308a01e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2023-c6137b5c66 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-587b305c8a has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-cae23d55ef has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2023-e10308a01e has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-aa62881cba has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2024-a8f27a60a0 (mmlib-1.4.2-13.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-a8f27a60a0 FEDORA-EPEL-2024-a8f27a60a0 (mmlib-1.4.2-13.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository. If problem still persists, please make note of it in this bug report. |