Difference between revisions of "User:Sardisson/madhatter"
Jump to navigation
Jump to search
(→BUGS: more) |
(→BUGS: add cloning failure) |
||
| Line 15: | Line 15: | ||
* Need to have self-update and tinder-config update generate a log so someone can at least check locally what's going on when they fail. Ideally, use the next build's log, but that's not set up yet, and return the purple (infra exception) status. | * Need to have self-update and tinder-config update generate a log so someone can at least check locally what's going on when they fail. Ideally, use the next build's log, but that's not set up yet, and return the purple (infra exception) status. | ||
* Clobber of mozilla sometimes fails: [http://hg.mozilla.org/users/alqahira_ardisson.org/madhatter/file/tip/build-seamonkey-util.pl#l1276] | * Clobber of mozilla sometimes fails: [http://hg.mozilla.org/users/alqahira_ardisson.org/madhatter/file/tip/build-seamonkey-util.pl#l1276] | ||
| + | * Failures cloning mozilla don't kill the build at that point (related to above?): [tinderbox log http://tinderbox.mozilla.org/showlog.cgi?tree=Camino&errorparser=unix&logfile=1311836580.1311837330.10857.gz&buildtime=1311836580&buildname=MacOSX%20Darwin%209.8.0%20cb-xserve04%20Depend%20Cm2.1-M1.9.2&fulltext=1] | ||
Revision as of 00:37, 28 July 2011
madhatter is a fork of the Tinderbox client that supports building from either CVS or Hg. It was hacked up by Smokey Ardisson to support Camino 2.1 development.
TODO
Usually marked XXX in the code, although some of them are from old tinderbox hackers; this list is not complete
- Show revision info for madhatter self-updates
- In theory, Hg checkout should support pull-by-date: [1], [2]
- Support different branches/tags in each repo
- Improve the changeset generation code and handle failures/errors: [3], [4]
BUGS
- (When building from a branch), getting the Gecko revision fails sometimes (Cm2.1b1)
- One option might be to get the info from
platform.ini/generated/*_changesetcache files in the Camino build, if they're empty. However, currently we do the revision-generation code after cloning rather than at TinderPrint time (so we know where we are in the filesystem), and those files don't exist before a build.
- One option might be to get the info from
- Need to have self-update and tinder-config update generate a log so someone can at least check locally what's going on when they fail. Ideally, use the next build's log, but that's not set up yet, and return the purple (infra exception) status.
- Clobber of mozilla sometimes fails: [5]
- Failures cloning mozilla don't kill the build at that point (related to above?): [tinderbox log http://tinderbox.mozilla.org/showlog.cgi?tree=Camino&errorparser=unix&logfile=1311836580.1311837330.10857.gz&buildtime=1311836580&buildname=MacOSX%20Darwin%209.8.0%20cb-xserve04%20Depend%20Cm2.1-M1.9.2&fulltext=1]
