[Geoserver-devel] Time issues with the Hudson build server?

GeoServer GeoServer Developer
1

Hi,
today, after noticing I broke the build, I committed a change
to fix it and then started a buil on gridlock.
The revision on my machine was 8461.

Now, look at the output of the Maven build I started on Hudson:

--------------------------------------------------------------------

Updating https://svn.codehaus.org/geoserver/trunk/geoserver

Fetching 'http://svn.codehaus.org/geoserver/trunk/configuration/minimal’ at -1 into '/home/tomcat/.hudson/jobs/geoserver-trunk/workspace/geoserver/community/community-schemas/web-c/minimal'

At revision 8461

Fetching 'http://svn.openlayers.org/tags/openlayers/release-2.4-rc1/img’ at -1 into '/home/tomcat/.hudson/jobs/geoserver-trunk/workspace/geoserver/community/community-schemas/web-c/src/main/webapp/openlayers/img'

At revision 6379

Fetching 'http://svn.openlayers.org/tags/openlayers/release-2.4-rc1/lib’ at -1 into '/home/tomcat/.hudson/jobs/geoserver-trunk/workspace/geoserver/community/community-schemas/web-c/src/main/webapp/openlayers/lib'

At revision 6379

Fetching 'http://svn.codehaus.org/geoserver/trunk/configuration/minimal’ at -1 into '/home/tomcat/.hudson/jobs/geoserver-trunk/workspace/geoserver/web/minimal'

At revision 8461

At revision 8460

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.

no change for https://svn.codehaus.org/geoserver/trunk/geoserver since the previous build

no change for http://svn.codehaus.org/geoserver/trunk/configuration/minimal since the previous build

no change for http://svn.openlayers.org/tags/openlayers/release-2.4-rc1/img since the previous build

no change for http://svn.openlayers.org/tags/openlayers/release-2.4-rc1/lib since the previous build

no change for http://svn.codehaus.org/geoserver/trunk/configuration/minimal since the previous build

--------------------------------------------------------------------

Do you see that? The update did run, but ended up on 8460 after
the update, and see this warning:

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.

Hmm.... can it be that the clock on gridlock is misbehaving or just
set to the wrong time?
Cheers
Andrea

2

yeah I faced the same problem a couple times, having to wait a sensible time
after a commit to run a build so it picks up the svn changes...

Gabriel
On Tuesday 26 February 2008 09:52:24 pm Andrea Aime wrote:

Hi,
today, after noticing I broke the build, I committed a change
to fix it and then started a buil on gridlock.
The revision on my machine was 8461.

Now, look at the output of the Maven build I started on Hudson:

--------------------------------------------------------------------

Updating https://svn.codehaus.org/geoserver/trunk/geoserver

Fetching 'http://svn.codehaus.org/geoserver/trunk/configuration/minimal’
at -1 into
'/home/tomcat/.hudson/jobs/geoserver-trunk/workspace/geoserver/community/co
mmunity-schemas/web-c/minimal'

At revision 8461

Fetching 'http://svn.openlayers.org/tags/openlayers/release-2.4-rc1/img’
at -1 into
'/home/tomcat/.hudson/jobs/geoserver-trunk/workspace/geoserver/community/co
mmunity-schemas/web-c/src/main/webapp/openlayers/img'

At revision 6379

Fetching 'http://svn.openlayers.org/tags/openlayers/release-2.4-rc1/lib’
at -1 into
'/home/tomcat/.hudson/jobs/geoserver-trunk/workspace/geoserver/community/co
mmunity-schemas/web-c/src/main/webapp/openlayers/lib'

At revision 6379

Fetching 'http://svn.codehaus.org/geoserver/trunk/configuration/minimal’
at -1 into
'/home/tomcat/.hudson/jobs/geoserver-trunk/workspace/geoserver/web/minimal'

At revision 8461

At revision 8460

WARNING: clock of the subversion server appears to be out of sync. This
can result in inconsistent check out behavior.

no change for https://svn.codehaus.org/geoserver/trunk/geoserver since
the previous build

no change for
http://svn.codehaus.org/geoserver/trunk/configuration/minimal since the
previous build

no change for
http://svn.openlayers.org/tags/openlayers/release-2.4-rc1/img since the
previous build

no change for
http://svn.openlayers.org/tags/openlayers/release-2.4-rc1/lib since the
previous build

no change for
http://svn.codehaus.org/geoserver/trunk/configuration/minimal since the
previous build

--------------------------------------------------------------------

Do you see that? The update did run, but ended up on 8460 after
the update, and see this warning:

WARNING: clock of the subversion server appears to be out of sync. This
can result in inconsistent check out behavior.

Hmm.... can it be that the clock on gridlock is misbehaving or just
set to the wrong time?
Cheers
Andrea

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

!DSPAM:4045,47c47c2065013668746562!

3

My bad, I've added ntpdate to local.start and a weekly one for good measure.

-Arne

Gabriel Roldán wrote:

yeah I faced the same problem a couple times, having to wait a sensible time after a commit to run a build so it picks up the svn changes...

Gabriel
On Tuesday 26 February 2008 09:52:24 pm Andrea Aime wrote:
  

Hi,
today, after noticing I broke the build, I committed a change
to fix it and then started a buil on gridlock.
The revision on my machine was 8461.

Now, look at the output of the Maven build I started on Hudson:

--------------------------------------------------------------------
..............................
Do you see that? The update did run, but ended up on 8460 after
the update, and see this warning:

WARNING: clock of the subversion server appears to be out of sync. This
can result in inconsistent check out behavior.

Hmm.... can it be that the clock on gridlock is misbehaving or just
set to the wrong time?
Cheers
Andrea