| Subject: | Seeing test failures under 5.10.1 |
~/rpmbuild/BUILD/Variable-OnDestruct-Scoped-0.001 $ prove -blv t/10-basics.t
t/10-basics.t ..
1..4
not ok 1 - Second array didn't trigger!
# Failed test 'Second array didn't trigger!'
# at t/10-basics.t line 22.
# got: '1'
# expected: '0'
ok 2 - Destructors were called
ok 3 - Destructors were not called again
not ok 4 - Destructors were called once more
# Failed test 'Destructors were called once more'
# at t/10-basics.t line 77.
# +----+------------+----+------------+
# | Elt|Got | Elt|Expected |
# +----+------------+----+------------+
# | 0|[ | 0|[ |
# | 1| 'array', | 1| 'array', |
# | 2| 'code', | 2| 'code', |
# | 3| 'glob', | 3| 'glob', |
# | | * 4| 'hash', *
# | 4| 'scalar' | 5| 'scalar' |
# | 5|] | 6|] |
# +----+------------+----+------------+
# Looks like you failed 2 tests of 4.
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/4 subtests
Test Summary Report
-------------------
t/10-basics.t (Wstat: 512 Tests: 4 Failed: 2)
Failed tests: 1, 4
Non-zero exit status: 2
Files=1, Tests=4, 0 wallclock secs ( 0.01 usr 0.00 sys + 0.08 cusr 0.01 csys = 0.10 CPU)
Result: FAIL
~/rpmbuild/BUILD/Variable-OnDestruct-Scoped-0.001 $ pmvers Exporter XSLoader
Exporter: 5.73
XSLoader: 0.24
If I change the first test to simply add "1;" or "my $foo" or anything really after "undef $self" it then succeeds.
As far as the second test I'm not sure why it fails.
BTW: Is this module meant to supersede Variable::OnDestruct entirely? They look almost identical description-wise.