QA/TDAI/Meetings/2006-12-18: Difference between revisions

m
Line 27: Line 27:
** All may not be appropriate to run per build interation
** All may not be appropriate to run per build interation
** JS tests take a couple hours to run - once per day
** JS tests take a couple hours to run - once per day
** [robcee] Main tests - ref tests - 10-15 seconds
** [robcee] Main buildbot tests now - RefTests - take 10-15 seconds
** Fast cycles tests - run per build
** Fast cycles tests - run per build
*** one VM per platform
*** one VM per platform
Line 35: Line 35:
** [bc] should probably do make-clobber builds - make-depend is not reliable
** [bc] should probably do make-clobber builds - make-depend is not reliable
* Buildbot should support debug builds, waytoomuch GC builds, or other special builds  
* Buildbot should support debug builds, waytoomuch GC builds, or other special builds  
* Bob's tools
* Bob's tools:
** checkout, clean (clobber), build, params for optomized or debug build
** Steps: checkout, clean (clobber), build
** Parameters: for optomized or debug build, etc
* Build FFx, TBird, XULRunner for all branches
* Build FFx, TBird, XULRunner for all branches
* buildbox master is on private network
* Buildbot master is on private network
** reports to tinderbox - public visibility
** Reports to tinderbox - public visibility
** impacts for sec tests?
** Impacts for sec tests on reporting?
* Need a couple xservs - RefTest and JS tests '''<<== AI timr'''
* Need a couple xservs - RefTest and JS tests '''<<== AI timr'''
** Mac Intel xservers - to replace the minis - for the CoLo
** Mac Intel xservers - to replace the minis - for the CoLo
* run 1.8 on one machine and 1.8.0 and 1.9 on another machine
* Run 1.8 on one machine and 1.8.0 and 1.9 on another machine
** so they all complete within a day
** So they all complete within a day


== Next steps for collecting /reporting results ==
== Next steps for collecting /reporting results ==
2,088

edits