Mailing List Archive

CI fails from mingw64
The github CI testing machine for Windows mingw64 always fails lately.

The details of the failure are:

re/uniprops01.t (Wstat: 2304 Tests: 0 Failed: 0)
Non-zero exit status: 9
Parse errors: No plan found in TAP output

because:

re/uniprops01.t ......................................................
Dubious, test returned 9 (wstat 2304, 0x900)
No subtests run

no deeper indications why.

It fails on every single commit/PR, in a way that none of the others
do; not even the Windows msvc142.

I've been ignoring it lately and I think so has everyone else.

Does anyone have a plan of what to do about it? Do we

0) Continue to ignore it

1) Remove it from the CI set as we don't seem to get any useful
information out of it

2) Investigate why it fails and maybe fix it?


I don't want to continue to have to remember to ignore that red X mark,
because I don't want to train myself into ignoring CI failures as doing
that will eventually cause me to overlook a real failure.

--
Paul "LeoNerd" Evans

leonerd@leonerd.org.uk | https://metacpan.org/author/PEVANS
http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/
Re: CI fails from mingw64 [ In reply to ]
On 6/15/21 10:39 AM, Paul "LeoNerd" Evans wrote:
> The github CI testing machine for Windows mingw64 always fails lately.

https://github.com/Perl/perl5/issues/18866


>
> The details of the failure are:
>
> re/uniprops01.t (Wstat: 2304 Tests: 0 Failed: 0)
> Non-zero exit status: 9
> Parse errors: No plan found in TAP output
>
> because:
>
> re/uniprops01.t ......................................................
> Dubious, test returned 9 (wstat 2304, 0x900)
> No subtests run
>
> no deeper indications why.
>
> It fails on every single commit/PR, in a way that none of the others
> do; not even the Windows msvc142.
>
> I've been ignoring it lately and I think so has everyone else.
>
> Does anyone have a plan of what to do about it? Do we
>
> 0) Continue to ignore it
>
> 1) Remove it from the CI set as we don't seem to get any useful
> information out of it
>
> 2) Investigate why it fails and maybe fix it?
>
>
> I don't want to continue to have to remember to ignore that red X mark,
> because I don't want to train myself into ignoring CI failures as doing
> that will eventually cause me to overlook a real failure.
>