* Michael Enright (michael.enri...@gmail.com) wrote:

> > Relevant excerpt:
> >
> > ---
> > <snip>
> >
> >   Process terminated due to timeout
> >
> > <snip>
> >
> > The question is obvious: where is this timeout defined, what value
> > is it set to exactly and is it tunable?
> >
> 
> When you build manually in this setup, does the build actually
> complete?

Of course.

> How long does it take for the compile to complete?

It's still hard to reproduce, however I've emulated it by writing a
Makefile which compiles, then links the test file taken from cmake with
the same compiler and flags as used in the build - essentially the same
thing which cmake does judging from the output.

I've ran this in a loop with package build runing in a parallel to
somehow simulate what's actually hapenning on our build cluster and
measured some times.

Host hardware is Core i7-2600K @ 3.40GHz (4 cores x 2 HT threads)

                            ( min /  avg / max )
              Build on host: 0.00 / 0.00 / 0.43 (fully native)
 ARMv6 jail, host toolchain: 0.03 / 0.27 / 3.76 (what we actually use for 
cross-builds)
ARMv6 jail, armv6 toolchain: 0.91 / 1.23 / 4.82 (fully emulated)

As you can see, it's not uncommon for the build to take several
seconds, and the timeout as I suspect is somewhere around this
value. I'd suggest to bump it to some arbitrary high value like 60
seconds, which, on one hand, ensures that the build doesn't hand,
on the other tolerates slow hardware and environments.

However, I doubt this solution (enforcing any timeouts by default)
in general, as there's no limit on how slow compilation could be
(slow hardware, emulation, CPU starvation due other tasks and/or
low priority, SIGSTOP etc.).

> It seems to me that if the compile is actually completing then
> worrying about CMake's timeout is worth the trouble.

-- 
Dmitry Marakasov   .   55B5 0596 FF1E 8D84 5F56  9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru  ..:  jabber: amd...@jabber.ru      http://amdmi3.ru
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Reply via email to