On Wed, May 14, 2014 at 1:25 AM, Dirkjan Ochtman <[email protected]> wrote: > On Tue, May 13, 2014 at 3:30 AM, Alexander Shorin <[email protected]> wrote: >> On Thu, May 8, 2014 at 11:03 AM, Dirkjan Ochtman <[email protected]> wrote: >>> On Tue, May 6, 2014 at 10:35 PM, Robert Kowalski <[email protected]> wrote: >>>> Test Summary Report >>>> ------------------- >>>> ../test/etap/075-auth-cache.t (Wstat: 0 Tests: 2 Failed: >>>> 1) >>>> Failed test: 2 >>>> Parse errors: Bad plan. You planned 19 tests but ran 2. >>>> Files=51, Tests=1198, 284 wallclock secs ( 0.53 usr 0.11 sys + 94.30 cusr >>>> 23.84 csys = 118.78 CPU) >>>> Result: FAIL >>>> make[1]: *** [check] Error 1 >>>> make: *** [distcheck] Error 1 >>> >>> Ugh. Do we have any ideas about this? >> >> Probably, another floating test failure, but I couldn't reproduce it >> no matter how I tried. > > So are we going to say this is a fluke and we'll leave it for now?
I would say yes (gritting one's teeth). We'd made not a single release with a lot of floating issues. Hopefully few the most annoying ones we'd fixed for 1.6, but we don't really know if this one is the last. For 1.7 we will have new, better test suite - that's the goal. @Robert If you have a chance, try to reproduce this failure in verbose mode: ./test/etap/run -v test/etap/075-auth-cache.t just wonder where it could fail for you. -- ,,,^..^,,,
