make Talos slaves on the same builder report as two different trees on Tinderbox

RESOLVED FIXED

Status

RESOLVED FIXED
11 years ago
5 years ago

People

(Reporter: bhearsum, Assigned: bhearsum)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

There's been some confusing and frustration since qm-pxp03 was brought back up. Because of the Tinderbox display the endtimes for builds are often inaccurate. As per the discussion in #developers we will keep both of these machines running but have them report as two seperate trees.
yes, we should do this, everyone I've talked to thinks that unless the numbers are reliably in the same range we shouldn't have them in the same column.  Its also hard to be sure when runs actually start/stop since there's overlap.
Created attachment 282542 [details] [diff] [review]
use a single tbox tree for each qm-pxp* machine

This patch makes each of the qm-pxp* machines report to a different Tinderbox tree. The minis are unchanged by this, if we want to do this for them in the future it will be trivial.

The code to do this is a bit hacky, so I've filed bug 397759 to get it a bit nicer, and something we can put in our Buildbot tree.

Rob, I noticed that I missed tinderbox.py in the big re-org patch, so I've included it here.
Attachment #282542 - Flags: review?(rcampbell)
Comment on attachment 282542 [details] [diff] [review]
use a single tbox tree for each qm-pxp* machine

tinderboxpoller is divergent from checked-in version. We should consolidate these at some point in another bug.
Attachment #282542 - Flags: review?(rcampbell) → review+
Created attachment 282740 [details] [diff] [review]
same as before, proper comments

Same patch as before, but using "#" instead of "//" for the comments. (It turns out python doesn't recognize "//" as a comment, whould've thunk it!)
Attachment #282740 - Flags: review?(rcampbell)
Comment on attachment 282740 [details] [diff] [review]
same as before, proper comments

oh, uh, I should've picked up on that. My bad...
Attachment #282740 - Flags: review?(rcampbell) → review+
Checking in master.cfg;
/cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/master.cfg,v  <--  master.cfg
new revision: 1.7; previous revision: 1.6
done
RCS file: /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/tinderboxmailnotifier.py,v
done
Checking in tinderboxmailnotifier.py;
/cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/tinderboxmailnotifier.py,v  <--  tinderboxmailnotifier.py
initial revision: 1.1
done
RCS file: /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/tinderboxpoller.py,v
done
Checking in tinderboxpoller.py;
/cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/tinderboxpoller.py,v  <--  tinderboxpoller.py
initial revision: 1.1
done
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
Mass move of Core:Testing bugs to mozilla.org:ReleaseEngineering. Filter on RelEngMassMove to ignore.
Component: Testing → Release Engineering
Product: Core → mozilla.org
QA Contact: testing → release
Version: unspecified → other
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.