947
edits
Auto-tools/Projects/MozmillBuildbot: Difference between revisions
Auto-tools/Projects/MozmillBuildbot (view source)
Revision as of 21:59, 22 April 2010
, 22 April 2010→Tips: note about buildbot debugging
(notes on virtualenv, correction of dated priorities, and stub for buildbot debugging) |
(→Tips: note about buildbot debugging) |
||
| Line 48: | Line 48: | ||
* forcing builds through the web does not work. This is due to the fact that the build and the crashsymbols are downloaded must be downloaded from the [http://stage.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/ tinderbox builds] so the location of the desired build is unknown as they are indexed by time stamps (seconds since epoch). <tt>buildbot sendchange</tt> should instead be used to trigger a build for testing purposes. | * forcing builds through the web does not work. This is due to the fact that the build and the crashsymbols are downloaded must be downloaded from the [http://stage.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/ tinderbox builds] so the location of the desired build is unknown as they are indexed by time stamps (seconds since epoch). <tt>buildbot sendchange</tt> should instead be used to trigger a build for testing purposes. | ||
* | * debugging buildbot by running directly with twistd through the command line. buildbot, in general, is difficult to debug, as the log does not contain good summaries of the python errors encountered. As pointed out in http://osdir.com/ml/python.buildbot.devel/2007-10/msg00033.html , twistd may be directly on the master's buildbot.tac file for debugging: <tt>twistd -by master/buildbot.tac</tt> | ||
== Outstanding Work == | == Outstanding Work == | ||