Hi,

On a multi-configuration project, I encounter a systematic deadlock because the
parent job and one of its child are queued on the same node.

The configuration matrix is as follows:
[x] Build on multiple nodes
[-] Individual nodes
[x] APOLLON (apollon)
[x] CHRONOS (chronos)
[x] DEMETER (demeter)
[ ] EOS (eos)
[x] EROS (eros)
[x] PAN (pan)
[x] PONTOS (pontos)
[ ] master (the master Hudson node)
[+] Labels
[ ] Axes

Here is the console output:

started
Building remotely on PONTOS
Triggering label=PAN
Triggering label=APOLLON
Triggering label=DEMETER
Triggering label=PONTOS
Triggering label=EROS
Triggering label=CHRONOS

All jobs except the ones on "PONTOS" successfully terminate.
The parent job keeps executing, waiting for all its children termination, but it
never stops as the child job supposed to run on "PONTOS" remains in the build queue.

Enabling the master Hudson node has no effect. Its corresponding job also
remains in the build queue.

Thank you for reading.

Regards,
Regis.