Andy Seaborne wrote: > This is unstable because it run on Ubuntu1; in #8 it ran on Ubuntu2 and > passed. > > Is there anyway we can delete the state of everything and start again? > At the moment, CI fails quite frequently for no reason (i.e. when there > is no change to the codebase, and it fails in a deterministic test) > > Restricting it to Ubuntu2 seems pointless - a problem that will > resurface somewhere else. > > It's already set to "Always check out a fresh copy" > > (I've reordered the tests just for the sake of making a change as well) > > I don't get this error when running locally nor when I building for > Apache (mvn2 or mvn3).
ConfigTest.getTestingDirDB() is "tmp/testing/DB". init() creates those directories only once, if the static boolean initialized is false. TestTransRestart deletes that directory in the cleanup() method. TestTransRestart setup() method tries to recreate it via FileOps.ensureDir(path) which uses File.mkdir() (not mkdirs). Can this be the cause of the problems? It does not account for why does not fail on ubuntu2|4 or locally though. Could it be a file permissions issue? Using "/tmp" instead of a temporary directory in the workspace (i.e. "tmp") seems to solve this problem. Paolo
