Skip Menu |

This queue is for tickets about the Cache-Cache CPAN distribution.

Report information
The Basics
Id: 92600
Status: new
Priority: 0/
Queue: Cache-Cache

People
Owner: Nobody in particular
Requestors: ether [...] cpan.org
KENTNL [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 1.06
Fixed in: (no value)



Subject: Test Fails under Parallel Testing

Seems there are some shared paths between 2 or more tests causing unpredictable behaviour when those tests are run together.

Full build log showing failures attached.

But you can reproduce a subset of these failures (though it may take several runs to make it happen ) with:

 prove -b -j2 -vr t/3_test_file_cache.t  t/5_test_size_aware_file_cache.t
defined(@array) is deprecated at /home/kent/.cpanm/work/1391132572.279022/Cache-Cache-1.06/blib/lib/Cache/CacheTester.pm line 562.
    (Maybe you should just omit the defined()?)
===(       1;0   1/35   0/48 )==========================================defined(@array) is deprecated at /home/kent/.cpanm/work/1391132572.279022/Cache-Cache-1.06/blib/lib/Cache/CacheTester.pm line 562.
    (Maybe you should just omit the defined()?)
===(      65;18  33/35  32/48 )=========================================ok
t/5_test_size_aware_file_cache.t ..
ok 33
ok 34
ok 35
ok 36
ok 37
ok 38
ok 39
ok 40
ok 41
ok 42
ok 43
ok 44
ok 45
ok 46
ok 47
ok 48
Failed 5/48 subtests

Test Summary Report
-------------------
t/5_test_size_aware_file_cache.t (Wstat: 0 Tests: 48 Failed: 5)
  Failed tests:  10, 18, 24, 27, 29
Files=2, Tests=83, 23 wallclock secs ( 0.05 usr  0.00 sys +  0.24 cusr  0.07 csys =  0.36 CPU)
Result: FAIL
 


Running each test independently avoids failure case.

Subject: build.log

Message body is not shown because it is too large.

On 2014-01-30 17:53:00, KENTNL wrote: Show quoted text
> Seems there are some shared paths between 2 or more tests causing > unpredictable > behaviour when those tests are run together.
It looks like there is no way to use separate cache files in different bits of code! So this is a more serious issue than just in the tests -- any sort of parallelism will fail in the same way.