If you do not want to use Merge Requests despite other people in the
same project do, can you please consider at least adopting a workflow
that you check if Salsa CI passed before you upload?
Looking at
https://salsa.debian.org/debian/devscripts/-/commits/mainseems Yadd's commit 2f5cacf4 broke CI, which shows the autopkgtest
failure:
autopkgtest [22:26:30]: test metacpan: [-----------------------
# Test: simple_test
uscan.t die: Please install a sopv variant. at
/tmp/autopkgtest-lxc.se4bhzng/downtmp/build.Jn9/src/test/../lib/Devscripts/Uscan/Output.pm
line 83.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 2 just after 1.
t/uscan.t ..
ok 1 - use Devscripts::Uscan;
Dubious, test returned 2 (wstat 512, 0x200)
All 1 subtests passed
Test Summary Report
t/uscan.t (Wstat: 512 (exited 2) Tests: 1 Failed: 0)
Non-zero exit status: 2
Parse errors: No plan found in TAP output
Files=1, Tests=1, 1 wallclock secs ( 0.02 usr 0.01 sys + 0.41 cusr
0.10 csys = 0.54 CPU)
Result: FAIL
In
https://ci.debian.net/packages/d/devscripts/testing/amd64/63279888/we have now the same issue, and this package won't migrate to testing
and any other package that interacts with devscripts will have
autopkgtest failing and not migrating to testing either until it is
fixed:
autopkgtest [03:19:51]: test metacpan: [-----------------------
553s # Test: stable_version
553s uscan.t die: Please install a sopv variant. at
/tmp/autopkgtest-lxc.1ry6nate/downtmp/build.I4Q/src/test/../lib/Devscripts/Uscan/Output.pm
line 83.
553s # Tests were run but no plan was declared and done_testing() was not seen.
553s # Looks like your test exited with 2 just after 1.
553s t/uscan.t ..
553s ok 1 - use Devscripts::Uscan;
553s Dubious, test returned 2 (wstat 512, 0x200)
553s All 1 subtests passed
553s
553s Test Summary Report
Thanks!