Thanks, Chris. It seems the build is working again now.
I was not involved in earlier attempts to set up a Windows build for Jackrabbit, but other PMC members noted that Windows slaves are more unstable than Linux ones, so for us it would be great to know that intermittent errors that are out of control are minimised, so we don't need to bug you anytime something goes wrong :-) Thanks, Robert On Thu, 2017-12-21 at 08:09 -0500, Chris Thistlethwaite wrote: > I'll take a look this morning, the failed build was likely due to a > Jenkins restart and we've seen the locked file issue before. Let me > clean up the node and I'll kick off another build. > -Chris T > On Thu, 2017-12-21 at 13:24 +0200, Robert Munteanu wrote: > > Hi, > > > > On Thu, 2017-11-30 at 20:54 +0000, Chris Thistlethwaite wrote: > > > > > > Greetings, > > > > > > Good news everyone! We've been working on puppetizing Windows > > > Jenkins > > > nodes and have a new build VM that could use some testing and > > > burn- > > > in. > > > I'm looking for volunteers to point their build to jenkins- > > > win2016- > > > 1 > > > to > > > iron out any issues. There are some changes due to this box being > > > 2016 > > > instead of 2012, but I'm anticipating most updates to make it > > > back > > > into > > > the Puppet config. Once this node is officially live, we'll add > > > it > > > to > > > the Windows group and notify the list. > > > > Thanks for the work on setting up a new windows VM. I created a job > > for > > the Jackrabbit project at [1], which was working well for some > > time. > > > > Starting with with build #52 ( Dec 20, 2017 8:44 AM ) all builds > > have > > failed. In build #52, the console output is cut off abruptly during > > a > > module build, which suggests an unclean shutdown [2]. > > > > For reference, build #51 succeeded in the same day at 4:50 AM. > > > > As of #53, builds started failing with SVN errors [3]: > > > > Started by an SCM change > > [EnvInject] - Loading node environment variables. > > Building remotely on windows-2016-1 in workspace > > f:\jenkins\jenkins- > > slave\workspace\Jackrabbit-Oak-Windows > > Cleaning up f:\jenkins\jenkins-slave\workspace\Jackrabbit-Oak- > > Windows\. > > Deleting f:\jenkins\jenkins-slave\workspace\Jackrabbit-Oak- > > Windows\oak- > > blob-plugins\target > > ERROR: Failed to update https://svn.apache.org/repos/asf/jackrabbit > > /o > > ak > > /trunk > > .....(snip)...... > > Caused by: java.nio.file.FileSystemException: f:\jenkins\jenkins- > > slave\workspace\Jackrabbit-Oak-Windows\oak-blob-plugins\target\oak- > > blob-plugins-1.8-SNAPSHOT-tests.jar: The process cannot access the > > file > > because it is being used by another process. > > > > at > > java.base/sun.nio.fs.WindowsException.translateToIOException(Unknow > > n > > Source) > > at > > java.base/sun.nio.fs.WindowsException.rethrowAsIOException(Unknown > > Source) > > at > > java.base/sun.nio.fs.WindowsException.rethrowAsIOException(Unknown > > Source) > > at > > java.base/sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown > > Source) > > at > > java.base/sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unkn > > ow > > n > > Source) > > at java.base/java.nio.file.Files.deleteIfExists(Unknown Source) > > at hudson.Util.tryOnceDeleteFile(Util.java:290) > > at hudson.Util.tryOnceDeleteRecursive(Util.java:370) > > at hudson.Util.tryOnceDeleteContentsRecursive(Util.java:389) > > at hudson.Util.tryOnceDeleteRecursive(Util.java:369) > > at hudson.Util.deleteRecursive(Util.java:347) > > ... 33 more > > > > Can anyone look into why this happened? I am looking for an > > immediate > > fix but more importantly a solution ( which can be on our side, of > > course ) to make sure this doesn't happen again. > > > > Thanks! > > > > Robert > > > > > > [1]: https://builds.apache.org/job/Jackrabbit-Oak-Windows/ > > [2]: https://builds.apache.org/job/Jackrabbit-Oak-Windows/52/consol > > eT > > ex > > t > > [3]: https://builds.apache.org/job/Jackrabbit-Oak-Windows/53/consol > > e
