[Buildbot-commits] [SPAM] [Buildbot] #744: "queued" status for dependent builders
Buildbot
buildbot-devel at lists.sourceforge.net
Tue Mar 16 00:11:00 UTC 2010
#744: "queued" status for dependent builders
------------------------+---------------------------------------------------
Reporter: tfogal | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: undecided
Version: master | Keywords:
------------------------+---------------------------------------------------
I've got a scheduler which is dependent on my main build:
{{{
sched_visit = Scheduler(
name="sched-build",
branch=None,
treeStableTimer=2*60,
builderNames=["main-debian-lenny-amd64", "main-osuse-11.1-amd64",
"main-osx-10.5-x86"]
)
sched_tests_databases = Dependent(
name="sched-tests-databases",
upstream=sched_visit,
builderNames = ["test-db-s-debian-lenny-amd64",
"test-db-s-osuse-11.1-amd64",
"test-db-s-osx-10.5-x86"]
)
}}}
These share the same set of slaves; for example:
{{{
tjf_builders.append({
'name': "main-debian-lenny-amd64",
'slavenames': ["tjf-debian-lenny-amd64"],
'builddir': "main-%s" % "lenny-amd64",
'env': {'VISITARCH' : "bbot", 'BBDIR' : "lenny-amd64" },
'factory': f_incremental_visit,
'locks': [single_bld.access('counting')]
})
tjf_builders.append({
'name': "test-db-s-debian-lenny-amd64",
'slavenames': ["tjf-debian-lenny-amd64"],
'builddir': "test-db-s-%s" % "lenny-amd64",
'env': {'VISITARCH' : "bbot", 'BBDIR' : "lenny-amd64" },
'factory': f_tests_db,
'locks': [single_bld.access('counting')]
})
}}}
in the `/builders/` web interface, the `test-db-s` builders end up with a
status of "building" while the `main-` builders are running. This is a
bit confusing; it would be nicer if these said "Queued", or something else
to indicate they are not running, but will at some point.
--
Ticket URL: <http://buildbot.net/trac/ticket/744>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
More information about the Commits
mailing list