[Buildbot-devel] contradictory information from buildbot build

[Dustin J. Mitchell]

That sounds like a clock problem of some sort.

The 'elapsedTime' is measured on the buildslave.  The build start and
end times are measured on the master.  Is your windows clock somehow
running ridiculously fast?

Dustin

On Mon, Jun 30, 2014 at 12:25 PM, Michael L. <mlabbe at gmail.com> wrote:
> One of my ShellCommand buildsteps is returning with "command timed out: 3600
> seconds without output running" on my nightly build.  This rightly fails the
> build (haltOnFailure is True).
>
> However, when I look at the total elapsed build time, the duration of the
> build is 2 mins, 20 seconds.
>
> How is it possible that I am timing out after 3600 seconds if the build
> fails 140 seconds after starting?
>
> I am running BuildBot 0.8.8 and Twisted 14.0.0.  It is a Windows 7 Pro
> buildbot slave, running virtually.
>
> build step termination:
> command timed out: 3600 seconds without output running ['withvcvars.bat',
> 'amd64', 'python', 'compile_all_vendors.py', '--platform=Windows',
> '--arch=x64'], attempting to kill
> program finished with exit code 1
> elapsedTime=91310.0510000
>
> Looking at the build afterwards:
> Timing:
> Start Mon Jun 30 00:00:00 2014
> End Mon Jun 30 00:02:20 2014
> Elapsed 2 mins, 20 secs
>
>
> Michael Labbe
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>