Fedora Account System
Red Hat Associate
Red Hat Customer
perl-Mojo-IOLoop-ReadWriteProcess-0.23-4.fc32 fails to build in F32 because tests fail: $ prove -l t/10_cgroupv* t/10_cgroupv1.t .. 1/? Invalid path at lib/Mojo/IOLoop/ReadWriteProcess/CGroup/v1.pm line 30. # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 255 just after 1. t/10_cgroupv1.t .. Dubious, test returned 255 (wstat 65280, 0xff00) All 1 subtests passed t/10_cgroupv2.t .. 1/? Invalid path at lib/Mojo/IOLoop/ReadWriteProcess/CGroup.pm line 35. # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 255 just after 1. t/10_cgroupv2.t .. Dubious, test returned 255 (wstat 65280, 0xff00) All 1 subtests passed I thought it is triggered by a new systemd that enabled version 2 control groups but I cannot reproduce it in F31 with the same systemd, kernel and selinux-policy.
It's actually triggered by upgrading Mojolicious from 8.22 to 8.23. It provides the Mojo::File::path() that emits the warning.
Fixed by upgrading to version 0.24: https://koji.fedoraproject.org/koji/buildinfo?buildID=1402254
FEDORA-2020-9b88bdd987 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-9b88bdd987
FEDORA-2020-9b88bdd987 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-9b88bdd987` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-9b88bdd987 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-9b88bdd987 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.