Re: Smoke FAILs due to PERL_UNICODE

"H.Merijn Brand" <h.m.brand@xs4all.nl> wrote:
:I tried a bisect. *please* correct me if I did this wrong, so I can learn
:
[..]
:perl $ env PERL_UNICODE=3D"" /pro/bin/perl Porting/bisect.pl --target cpan/Pod-Simple/t/JustPod_corpus.t --start d4e32ec55bb4cf7
[...]
:skipping - Test case cpan/Pod-Simple/t/JustPod_corpus.t is not a readable file at /tmp/0gRcJIB7H9 line 1241.
:Runner returned 32000, not 0 for start revision at Porting/bisect.pl line 240.

`git log --stat cpan/Pod-Simple/t/JustPod_corpus.t` shows that the target
test file was added briefly in 314f4963 before being reverted in a0d36fc4;
it returned for real in 0478e945, all three occurring on May 24th. Your
start SHA is from May 13th, so the file does not yet exist.

If it passes at 0478e945, you should be able to provide that as the start.
If not, it has probably never passed in your environment.

HTH,

Hugo

• Smoke FAILs due to PERL_UNICODE by H.Merijn Brand
• Re: Smoke FAILs due to PERL_UNICODE by hv
• Re: Smoke FAILs due to PERL_UNICODE by Dave Mitchell