Opened 5 years ago

Closed 5 years ago

#46756 closed defect (wontfix)

p5-test-unit: add support for 5.18 5.20 5.22, other minor cleanups

Reported by: mojca (Mojca Miklavec) Owned by: blair (Blair Zajac)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: dbevans (David B. Evans)
Port: p5-test-unit

Description

Related to #46005 I would like to request addition of support for perl 5.18 and 5.20.

I'm attaching a patch that I used, but I get the following error report when running the tests:

PERL_DL_NONLAZY=1 /opt/local/bin/perl5.20 "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/all_tests.t ..... ok
t/assert.t ........ 
Failed 2/40 subtests 

 > The STDERR redirection may not work or may behave differently under
 > your OS 'darwin'. That will probably cause this test to fail.
t/try_examples.t .. ok

Test Summary Report
-------------------
t/assert.t      (Wstat: 0 Tests: 40 Failed: 2)
  Failed tests:  25, 37
Files=3, Tests=89,  2 wallclock secs ( 0.05 usr  0.02 sys +  1.96 cusr  0.17 csys =  2.20 CPU)
Result: FAIL
Failed 1/3 test programs. 2/89 subtests failed.
make: *** [test_dynamic] Error 255

There also exists a development version of the port (0.25_1325) which might have some bugs fixed.

Attachments (1)

p5-test-unit.p5.20.Portfile.patch (1.9 KB) - added by mojca (Mojca Miklavec) 5 years ago.

Download all attachments as: .zip

Change History (6)

Changed 5 years ago by mojca (Mojca Miklavec)

comment:1 Changed 5 years ago by mojca (Mojca Miklavec)

Summary: p5-test-unit: add support for 5.18 5.20, other minor cleanupsp5-test-unit: add support for 5.18 5.20 5.22, other minor cleanups

See also #48313

comment:2 Changed 5 years ago by mojca (Mojca Miklavec)

Given that the module is broken, that there was no input or feedback for the last 5 months and given that the last stable release of this module was 10 years ago (http://search.cpan.org/~mcast/Test-Unit-0.25/) – is this port needed at all? No other port depends on it, even though it could be that some modules would use it for writing the test cases (which is something I wasn't able to find out).

If the port is no longer needed, it might be easier to remove it and only add it back if it turns out that users want to have it. Blair, what's your opinion about this?

comment:3 Changed 5 years ago by blair (Blair Zajac)

I'm OK with removing it or giving ownership to somebody else, as I don't code in perl now.

comment:4 Changed 5 years ago by mojca (Mojca Miklavec)

In that case I suggest removing this port, at least until someone asks for it.

comment:5 Changed 5 years ago by mojca (Mojca Miklavec)

Resolution: wontfix
Status: newclosed

I removed the port in r141750.

Note: See TracTickets for help on using tickets.