Hi again David, This is another offering of MSWin32 testing to you for one of your modules (see dagolden/Path-Tiny#223). If needed, further information about the AppVeyor CI config is available at rivy/CI.AppVeyor.helpers-perl.
This PR results in an AppVeyor CI report which is a bit more problematic.
Essentially, it seems "Devel::Cover" doesn't play well with fork under MSWin32. For example, when using fork/Devel::Cover together under Windows/MSWin32 (with various perl versions up to v5.28 and $Devel::Cover::VERSION == 1.31), I get frequent failures of otherwise working tests with messages similar to the following ...
C:\>rem from File::Temp
C:\>prove -bl t\fork.t
[19:45:17] t\fork.t .. 1/8
Unfortunately, Devel::Cover does not yet work with threads. I have done
some work in this area, but there is still more to be done.
[19:45:17] t\fork.t .. Dubious, test returned 3 (wstat 768, 0x300)
Failed 7/8 subtests
So, the initial testing job which includes coverage fails many of the tests in 't/10-stdout-string.t', 't/11-stderr-string.t', and 't/25-cap-fork.t'. My initial impulse would be to just disable the forking tests, but there are a lot of tests which include fork logic which are completing successfully.
That job combination is marked as an "Allowed failure" and so doesn't break the test build, but there are are a few additional build-breaking single failures for the jobs testing perl versions v5.10, v5.8.9, and v5.8.8. These might have real causes.
Sorry to hand you a package with some rough edges, but I'm not quite sure how to polish them down.
As before, I hope you'll find this useful, and let me know if I can help track down fixes to the tests.
rivy
commented
5 years ago
Hi again David, This is another offering of MSWin32 testing to you for one of your modules (see dagolden/Path-Tiny#223). If needed, further information about the AppVeyor CI config is available at rivy/CI.AppVeyor.helpers-perl.
This PR results in an AppVeyor CI report which is a bit more problematic.
Essentially, it seems "Devel::Cover" doesn't play well with fork under MSWin32. For example, when using fork/Devel::Cover together under Windows/MSWin32 (with various perl versions up to v5.28 and $Devel::Cover::VERSION == 1.31), I get frequent failures of otherwise working tests with messages similar to the following ...
So, the initial testing job which includes coverage fails many of the tests in 't/10-stdout-string.t', 't/11-stderr-string.t', and 't/25-cap-fork.t'. My initial impulse would be to just disable the forking tests, but there are a lot of tests which include fork logic which are completing successfully.
That job combination is marked as an "Allowed failure" and so doesn't break the test build, but there are are a few additional build-breaking single failures for the jobs testing perl versions v5.10, v5.8.9, and v5.8.8. These might have real causes.
Sorry to hand you a package with some rough edges, but I'm not quite sure how to polish them down.
As before, I hope you'll find this useful, and let me know if I can help track down fixes to the tests.