Hi list,

I am just puzzling about some strange behaviour of my master/slave
setup. I have a 4 core master with Win7/64 bit and about 10 slaves
with 2 cores and Win7/64 bit/Win2008 Server R2. I compile a .NET
project at 20:00 and start (at the moment as a scheduled job at 21:00)
about 150 unit test projects to keep the cluster chewing during night.
If you look at the attached picture you can see that there are about
120 queued jobs when the test projects start which get less over time.
Somewhere around 2:30 the number of occupied executors begins to drop
and no queued job gets executed any more. At 5:30 the regular nightly
compile and setup generation of our software is started, but it is
only queued and there is _no_ dependency to the unit test jobs (block
build because up/downstream job is running). Suddenly at around 7:00
the queued jobs begin to be executed again.

There is nothing conspicuous in the logs of the jobs. Any ideas if
this is a known bug or where I could look for direct Jenkins logs
telling me why a job is waiting and not executed?

Thanks for hints
Dirk

<<attachment: Load.png>>

Reply via email to