So I am like everybody else. The test works for me. My suspicion is that there is something going on with the temporary directory that I am trying to use and that the environment that Jenkins is using is somehow strange.
The only slightly surprising idiom I am using is to create a temporary file, delete it and recreate it as a directory. I even check the return values from the delete and the mkdir. I will keep looking. On Tue, Dec 27, 2011 at 10:37 PM, Ted Dunning <ted.dunn...@gmail.com> wrote: > Indeed it does. Thanks for pointing that out. > > This error is very strange. > > > On Tue, Dec 27, 2011 at 10:06 PM, Dmitriy Lyubimov <dlie...@gmail.com>wrote: > >> Ted, >> >> do you have an idea why this test may be failing? I think this test comes >> with M-792 commit. >> >> I can take a look at it, I suspect something in the environment can be >> tripping it. >> On Dec 27, 2011 8:54 PM, "Sean Owen" <sro...@gmail.com> wrote: >> >> > It's all errors in the Apache infrastructure, rather than a real test >> > failure. At least, stuff passes for me locally, and that's what's >> > important. >> > So I'm ignoring these. >> > >> > On Tue, Dec 27, 2011 at 9:34 PM, Jeff Eastman >> > <jeast...@windwardsolutions.com> wrote: >> > > I'm getting a lot of these emails yet all the tests run locally for >> me. >> > Does >> > > anybody have an idea what the problem is? This close to a release it >> > would >> > > be really nice to have Jenkins on our side. >> > > Jeff >> > > >> > >> > >
