Bug 2037572
Summary: | perl-Test2-Harness-1.000095 is available | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
Component: | perl-Test2-Harness | Assignee: | Petr Pisar <ppisar> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | perl-maint, ppisar |
Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | perl-Test2-Harness-1.0.95-1.fc36 perl-Test2-Harness-1.0.101-1.fc35 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-02-12 01:18:14 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
Upstream Release Monitoring
2022-01-06 00:56:18 UTC
Latest upstream release: 1.000095 Current version/release in rawhide: 1.0.93-1.fc36 URL: https://metacpan.org/release/Test2-Harness Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/21137/ A bug-fix release suitable for Fedora ≥ 35. F35 update waits on stabilizing perl-Test2-Harness-1.0.93-1.fc35. A test fails in CI: ./t/integration/resource.t ................. ok # Failed test 'Exit Value Check' # at ./t/integration/reload_syntax_error.t line 91. # +-----+----+-------+ # | GOT | OP | CHECK | # +-----+----+-------+ # | 256 | eq | 0 | # +-----+----+-------+ # Command = /usr/bin/perl /usr/bin/yath -D/usr/share/perl5/vendor_perl run ./t/integration/reload_syntax_error.tx :: fixed # Exit = 256 # ==== Output ==== # (INTERNAL) 16816 yath-nested-runner-A - Runner detected a change in one or more preloaded modules... # (INTERNAL) 16816 yath-nested-runner-A - blacklisting changed files and reloading stage... # (INTERNAL) 16832 yath-nested-runner-A - Runner detected a change in one or more preloaded modules... # (INTERNAL) 16832 yath-nested-runner-A - blacklisting changed files and reloading stage... # (INTERNAL) Global symbol "$bob" requires explicit package name (did you forget to declare "my $bob"?) at /tmp/hSUtsRJ_Pf/Preload/Flux.pm line 7. # (INTERNAL) Compilation failed in require at (eval 168) line 1. # ( FAILED ) job 1 t/integration/reload_syntax_error.tx # < REASON > job 1 Test script returned error (Signal: 1) # < REASON > job 1 No plan was declared, and no assertions were made. # # The following jobs failed: # +------------------------------------+------------------------------------+ # | Job ID | Test File | # +------------------------------------+------------------------------------+ # | 9120EFE6-7F64-11EC-8AFB-B6B697C7AB | t/integration/reload_syntax_error. | # | 9E | tx | # +------------------------------------+------------------------------------+ # # Yath Result Summary # ----------------------------------------------------------------------------------- # Fail Count: 1 # File Count: 1 # Assertion Count: 0 # Wall Time: 1.62 seconds # CPU Time: 0.87 seconds (usr: 0.28s | sys: 0.12s | cusr: 0.29s | csys: 0.18s) # CPU Usage: 53% # --> Result: FAILED <-- # [0m # # ======== # Failed test 'yath run ./t/integr[...]x_error.tx :: fixed' # at ./t/integration/reload_syntax_error.t line 91. # Seeded srand with seed '20220127' from local date. ./t/integration/reload_syntax_error.t ...... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/5 subtests There are many similar failures on CPAN Testers Matrix <http://matrix.cpantesters.org/?dist=Test2-Harness+1.000095>. This build was held by CI, but relengs rebuilt it in F36 mass rebuild as perl-Test2-Harness-1.0.95-2.fc36 and tagged it directly to F36 bypassing CI. 1.000096 (bug #2046568) promises some fixes. FEDORA-2022-fbfdc398ff has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-fbfdc398ff FEDORA-2022-fbfdc398ff has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-fbfdc398ff` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-fbfdc398ff See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-d623405ad2 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-d623405ad2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d623405ad2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-cee59c9ecf has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-cee59c9ecf` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-cee59c9ecf See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-cee59c9ecf has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. |