Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: With python-opentelemetry-contrib 1.23.0/0.44b0[1][2], I’m seeing failures like _________________________________ test_timing __________________________________ tests/test_metrics.py:112: in test_timing (envelope,) = envelopes E ValueError: too many values to unpack (expected 1) in most of my local mock builds, and occasional failures like ____________________________ test_timing_decorator _____________________________ tests/test_metrics.py:180: in test_timing_decorator (envelope,) = envelopes E ValueError: too many values to unpack (expected 1) I’m planning to build this update in F40 and F41 soon, but I want to allow enough time for python-sentry-sdk to adapt. I tried to reproduce the problem in COPR[3], but of all the builds on F40 and F41, only the build on ppc64le on F41 failed[4]. The flakiness and the discrepancy between COPR and local builds seems to support the idea that the problem is one of timing – something is running faster or slower after the python-opentelemetry-contrib than this test expects – rather than a true incompatibility. Although I haven’t been able to reproduce the problem with the currently-packaged python-opentelemetry-contrib 1.22.0/0.43b0, I wonder if it might be possible in certain environments and/or with lower probability. Version-Release number of selected component (if applicable): 1.39.2-2 How reproducible: Steps to Reproduce: 1. In mock or in COPR, build [1]. 2. In mock or in COPR, using the results of [1], build [2]. 3. In mock or in COPR, using the results of [1] and [2], build python-sentry-sdk. Actual results: Flaky failures of test_timing and (with lower probability) test_timing_decorator, with frequency depending on environment. Expected results: Tests always pass. Additional info: If there is no response to this bug, I plan to proceed with the update in one week, on 2024-03-02 or slightly later. For F40, this means the update will not reach stable until the end of the Beta Freeze. If you ask me for more time to investigate, I’m happy to delay the update, although I would still like to have this in F40 before the Final Freeze, scheduled for 2024-04-02. [1] https://src.fedoraproject.org/rpms/python-opentelemetry/pull-request/12 [2] https://src.fedoraproject.org/rpms/python-opentelemetry-contrib/pull-request/7 [3] https://copr.fedorainfracloud.org/coprs/music/opentelemetry-1.23/packages/ [4] https://copr.fedorainfracloud.org/coprs/music/opentelemetry-1.23/build/7055251/
I just did a scratch-build of python-sentry-sdk in the same side tag with the opentelemetry/opentelemetry-contrib updates for F41, https://koji.fedoraproject.org/koji/taskinfo?taskID=114462898, and it was successful. So that’s a good sign that this is not too flaky to get successful builds in production Koji at least some of the time.
This stroke again; see: https://src.fedoraproject.org/rpms/python-sentry-sdk/pull-request/10#comment-210847 (from https://kojipkgs.fedoraproject.org/work/tasks/902/120920902/build.log). I have temporarily disabled these tests in https://src.fedoraproject.org/rpms/python-sentry-sdk/pull-request/10 until they will be reimplemented using mocking time, as described in https://github.com/getsentry/sentry-python/issues/3335.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42.
This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-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 '42'. 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. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 42 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 42 entered end-of-life (EOL) status on 2026-05-27. Fedora Linux 42 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.