Our Mozmill boxes have been running on staging (http://tinderbox.mozilla.org/ThunderbirdTest/) for a while now. With the new testing policy we should also be looking at getting these to run on trunk. This is the tracking bug for making that happen. As the MozMill boxes currently tend to be orange most of the time, I don't think we can sensibly switch them over to the production trees straight away. Instead I propose that this bug will track the following: - Any work required on the infrastructure to improve the integration with buildbot/make the roll-out easier. - Bugs that are currently causing the mozmill boxes to be orange. If anyone has time to help me with filing bugs on the oranges (especially non-mac osx), please chat to me over irc - don't necessarily go from what the tinderboxes say (e.g. I think the linux branches may be bust due to a trunk issue).
installed jsbridge==2.3.4 mozrunner==2.4 mozmill==1.4 on: momo-vm-04 momo-vm-06 momo-vm-13 momo-vm-15 momo-vm-16 momo-vm-win2k3-01 momo-vm-win2k3-03 momo-vm-win2k3-04 momo-vm-win2k3-05 momo-vm-win2k3-06 momo-vm-win2k3-07 momo-vm-win2k3-08 momo-vm-win2k3-09 momo-vm-win2k3-10
Whiteboard: [Windows live][Mac/Linux waiting on permanent/random oranges]
Whiteboard: [Windows live][Mac/Linux waiting on permanent/random oranges] → [Windows & Mac live][Linux waiting on permanent/random oranges]
Andrew fixed the remaining Linux perma orange in Bug 633498. These boxes are now running on production, so this bug is fixed.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 3.3a3
Whiteboard: [Windows & Mac live][Linux waiting on permanent/random oranges]
You need to log in before you can comment on or make changes to this bug.