Bug #86125 for File-NFSLock: Tests go up in flames under HARNESS_OPTIONS=j10

> Thu Jun 13 18:01:56 2013: Request 86125 was acted upon. > Transaction: Ticket created by KENTNL > Queue: File-NFSLock > Subject: Tests go up in flames under HARNESS_OPTIONS=j10 > Broken in: 1.21 > Severity: Normal > Owner: Nobody > Requestors: KENTNL@cpan.org > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=86125 > > > > Usually this issue indicates either that 2 tests have an interdependence of > some kind, either > > a: one test relies on a previous test being run to provide the right > scenario > for unning under > b: two tests inadvertently do IO of some kind to the same path, and tests > see > IO that they didn't expect as a result. > > #b usually just means you've got tests not using File::Temp > > Here, you can see it runs just fine on a standard single threaded test run: > https://gist.github.com/kentfredric/5777704 > > However, here is the catastrophe you get when you run tests in parallel: > > https://gist.github.com/kentfredric/5777727 > > The summary of which is: > > t/220_ex_scope.t (Wstat: 512 Tests: 11 Failed: 2) Failed tests: 7, 11 > Non-zero > exit status: 2 t/120_single.t (Wstat: 256 Tests: 2 Failed: 1) Failed test: > 2 > Non-zero exit status: 1 t/230_double.t (Wstat: 512 Tests: 5 Failed: 2) > Failed > tests: 4-5 Non-zero exit status: 2 t/210_nb_ex.t (Wstat: 256 Tests: 8 > Failed: 1) > Failed test: 8 Non-zero exit status: 1 t/400_kill.t (Wstat: 256 Tests: 10 > Failed: 1) Failed test: 10 Non-zero exit status: 1 t/300_bl_sh.t (Wstat: > 5376 > Tests: 73 Failed: 21) Failed tests: 53-73 Non-zero exit status: 21 > t/200_bl_ex.t (Wstat: 256 Tests: 22 Failed: 1) Failed test: 22 Non-zero > exit > status: 1Files=12, Tests=159, 14 wallclock secs ( 0.10 usr 0.04 sys + 0.75 > cusr > 0.49 csys = 1.38 CPU) > > Here's the parallel run again, but without OVER NINE THOUSAND lines of > "closed > file handle" warnings. > > https://gist.github.com/kentfredric/5777752 > >