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
Bisect points to v5.19.2-138-g137da2b05b; from that commit through to the end of the 5.19.x dev track the test HashBase.t fails for Test-Simple-1.302162 and as far as I can see for all Test-Simple 1.302xxx.
I have not sent any of the reports to cpantesters. Let me know if you need further details.
My motivation for writing this issue is that I had the itch to bisect through 5.19 for POD::Tested and could not do it with any version of Test::Simple that I tried.
The text was updated successfully, but these errors were encountered:
I should have added that of course there are ways to supply the right versions of dependent modules such that POD-Tested becomes bisectable. So this in not the point. The point is that a high - river toolchain infrastructure module would do better if it covered the historical dev bleadperl ranges in order to make bisecting convenient and not a thing that costs manual intervention.
Thanks, Matthew, for the suggestion. Will keep that option in mind next time I face such a situation. Actually, I was not talking about Porting/bisect-runner.pl but about bisecting in general. I should probably have considered using bisect-runner.pl.
Bisect points to v5.19.2-138-g137da2b05b; from that commit through to the end of the 5.19.x dev track the test HashBase.t fails for Test-Simple-1.302162 and as far as I can see for all Test-Simple 1.302xxx.
I have not sent any of the reports to cpantesters. Let me know if you need further details.
My motivation for writing this issue is that I had the itch to bisect through 5.19 for POD::Tested and could not do it with any version of Test::Simple that I tried.
The text was updated successfully, but these errors were encountered: