Working on cleaning disk space now...

On Tue, Jan 20, 2015 at 2:09 PM, Marshall Schor <m...@schor.com> wrote:

> A few messages earlier, I too had reported for a different job the same
> "out of
> space" problem.
>
> can someone take a look?
>
> -Marshall Schor
>
> On 1/20/2015 5:38 AM, Andy Seaborne wrote:
> > We have some bit rot in our Jenkin windows job:
> >
> > https://builds.apache.org/job/Jena_Development_Test_Windows/
> >
> > I can't even wipe the workspace at the moment.
> >
> > windows2:
> >
> > java.io.FileNotFoundException:
> C:\Windows\TEMP\junit2341214733363083535\folder
> > with space\file with space.ttl.new (There is not enough space on the
> disk)
> >     at java.io.FileOutputStream.open(Native Method)
> >
> > windows1:
> >
> > ERROR: Failed to clean the workspace
> > java.nio.file.FileSystemException:
> >
> f:\hudson\hudson-slave\workspace\Jena_Development_Test_Windows\jena-fuseki2\jena-fuseki-core\target\surefire\surefirebooter8715067708678023501.jar:
> > The process cannot access the file because it is being used by another
> process.
> >
> > and even after that the windows test job is failing because there
> appears to
> > be a background Jetty server from a previous run sitting on the test
> port 3535
> > but all the previous jobs seem to have finished and their JVMs exited.
> >
> > Things start going wrong after:
> >
> >
> https://builds.apache.org/view/All/job/Jena_Development_Test_Windows/507/
> >
> > where there is some low level Windows memory mapped file issues then the
> tests
> > either don't clean properly or can't because of the low level errors.
> >
> > Could some one please take a look?
> >
> > (In case it's our test procedures that are the cause I've disabled the
> jenkins
> > job.  Our windows job have been reported to be resource heavy
> > because of using more temporary space than our Linux ones - can't delete
> > memory mapped files on Windows while the JVM is running - but it has been
> > running OK for some time previously.)
> >
> >     Thanks
> >     Andy
> >
> >
>
>

Reply via email to