My interpretation of 'recheck out with a clobber' was to change the SVN
options of the Windows build
(https://builds.apache.org/job/ODFToolkit-windows/configure) to check
out a fresh trunc instead of using a 'svn update'.
After that I have triggered a build.
Going to keep this configuration, as I do not want to test SVN, but a
fresh clean trunk.
PS: I suggest to give Rob Jenkins access rights, so the fisher is able
to fish for a life time.. ;)
First fishes can be found at http://wiki.apache.org/general/Jenkins
Cheers,
Svante
On 04.06.2012 14:01, Rob Weir wrote:
Svante or Yegor, is this something you can help with? I don't have
Jenkins access rights. It looks like we're going to get hourly errors
until someone does a clean check out.
-Rob
On Mon, Jun 4, 2012 at 1:16 AM, Gavin McDonald<[email protected]> wrote:
-----Original Message-----
From: Rob Weir [mailto:[email protected]]
Sent: Monday, 4 June 2012 7:45 AM
To: [email protected]
Cc: [email protected]
Subject: Checksum mismatch on hudson-slave
https://builds.apache.org/job/ODFToolkit-windows/12/
https://builds.apache.org/job/ODFToolkit-windows/12/console
The only recent change was updating a README file.
There is a mention of that file in the log, an svn checksum mismatch error:
Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: Checksum
mismatch for 'F:\hudson\hudson-slave\workspace\ODFToolkit-
windows\trunk\.svn\text-base\README.txt.svn-base';
recorded: '6ae3d193a2a3f7cde4aae7102b271bd6', actual: 'null'
What does this mean, and what can we do about it?
I replaced a drive in the windows machine with a larger capacity.
Ignore the error, recheck out with a clobber.
Gav...
-Rob
