This is repeatedly going wrong and I'm not sure why.
On the surface, it looks like there is a rogue Jetty sitting on port
3535 which then blocks the tests.
But:
1/ Tracing back to the last job to run at all (#507), it's some TDB/JDBC
tests failing for weird low level reasons.
2/ Switch between windows1 and windows2 slaves today gets nasty file
errors (various flavours - some clearly jenkins problems)
3/ I can't even wipe the workspace at the moment.
so my guess is that OS resources are the problem and we can't fix them.
I've email builds@ to ask for help and disabled the job for now.
We might be contributing to the problems; the windows builds being
resource hungry for mmap files, but the job was running fine for quite
some time until #507 and I can't see any change that might be connected.
Andy
