Closed Bug 413553 Opened 17 years ago Closed 16 years ago

repurpose pear and plum for automated js testing

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rcampbell, Assigned: rcampbell)

References

Details

(Whiteboard: [checked-in, re-configuring master])

Attachments

(1 file)

These vms have been part of the qa farm for some time. They can be automated to run the branch js tests using the sisyphus buildbot master.

Patch includes some restructuring of the buildbot master. The config file loaded properly in my local environment so it shouldn't have any (obvious) errors in it.
Attachment #298539 - Flags: review?(bclary)
Comment on attachment 298539 [details] [diff] [review]
pear plum buildbot patch

I didn't see any obvious errors either. As soon as I land the patch for bug 406196 we will be able to substantially reduce the expected time for a browser run to complete.

Don't forget to turn on tinderbox scraping for pear and plum. 

Thanks!
Attachment #298539 - Flags: review?(bclary) → review+
cvs commit: Examining .
Checking in master.cfg;
/cvsroot/mozilla/tools/buildbot-configs/testing/sisyphus/master.cfg,v  <--  master.cfg
new revision: 1.7; previous revision: 1.6
done
Whiteboard: [checked-in, re-configuring master]
Status: NEW → RESOLVED
Closed: 16 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: Trunk → other
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: