#624: Add Latent BuildSlave for DRMAA supporting systems
---------------------------+-----------------------
Reporter: smackware | Owner:
Type: enhancement | Status: reopened
Priority: major | Milestone: 0.8.+
Version: | Resolution:
Keywords: virtualization |
---------------------------+-----------------------
Comment (by mvpel):
I found what may be an issue in Enrico's code or possibly the HTCondor
code, in that when jobs are sent to a remote scheduler's queue as a result
of having the "SCHEDD_HOST" config value set to the remote machine's
hostname, the job ID provided by DRMAA uses the local hostname instead of
the remote:
DRMAA-provided job ID: buildbot_host.23456.0
Actual Job ID? sched_host.23456.0
It comes back with an invalid job ID exception when it tries to DRMAA-
terminate the former. I can tell at least that the HUP signal is working
well because the slave goes promptly and gracefully away when I condor_rm
the job. I've set up the buildbot host with its own schedd queue, and
we'll see what happens.
--
Ticket URL: <http://trac.buildbot.net/ticket/624#comment:23>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
