You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This test script calls the Dev::UnitTest::Run command module. The effect is that the TAP from the script and from the command are combined, which throws TAP::Parser off the track.
Essentially we have:
1..2
ok 1 - UnitTest 'NutsAndBolts.t' not executed because blacklisted
1..1
ok 1 - easy success in NutsAndBolts.t
ok 2 - UnitTest 'NutsAndBolts.t' executed because not blacklisted
The lines 3 and 4 are printed by Dev::UnitTest::Run and shouldn't be there.
The text was updated successfully, but these errors were encountered:
Let's fix this for 10.0.4 as the test suite now uses TAP::Harness there too.
The reason why this happens is not obvious, so let's create a workaround. Call skip_allwhen a env var is set.
This test script calls the
Dev::UnitTest::Run
command module. The effect is that the TAP from the script and from the command are combined, which throws TAP::Parser off the track.Essentially we have:
The lines 3 and 4 are printed by
Dev::UnitTest::Run
and shouldn't be there.The text was updated successfully, but these errors were encountered: