#1966: Buildstep throws an unhandled error if it has alwaysRun=True and
buildslave
is lost
---------------------+---------------------------------
Reporter: JustAMan | Owner:
Type: defect | Status: new
Priority: minor | Milestone: undecided
Version: 0.8.0 | Keywords: alwaysrun exception
---------------------+---------------------------------
It occurs because probably no one considered such a case, thus there's no
check if BuildStep.remote is valid instance. In the case when buildslave
is lost it's equal to None.
I've created a patch to fix such an issue. It stops the build altogether
if build's remote went away, even if there are any buildsteps which have
alwaysRun=True set.
--
Ticket URL: <http://trac.buildbot.net/ticket/1966>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
