User:Rcampbell/1:30 Build Infrastructure notes: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Build farm infrastructure update and discussion]] | [[Build farm infrastructure update and discussion]] | ||
[http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox] | |||
paul: mozilla tools tinderbox-configs | paul: mozilla tools tinderbox-configs | ||
| Line 8: | Line 10: | ||
make check | make check | ||
rhelmer: Tinderbox currently runs "make test" or could run "make perftest" | |||
boris/dbaron: performance tests should run on slow boxes, correctness tests should run as quickly as possible. Dbaron notes that correctness tests, if done possible should take quite a while. | |||
schrep: can see need for three classes of machines: builds, performance, correctness. | |||
schrep: conceivably having a build system analogous to Java+Junit+Ant where a make target could invoke a set of tests and output the results to a text or xml file for Tinderbox to pick up. This allows developers to run tests as well as have them automatically invoked in tinderbox. | |||
Revision as of 21:18, 28 June 2006
Build farm infrastructure update and discussion
paul: mozilla tools tinderbox-configs
Update information on the wikis to be more accurate.
dbaron: Build targets should be added to client,mk and not restricted to Tinderbox. There is some consensus.
make check
rhelmer: Tinderbox currently runs "make test" or could run "make perftest"
boris/dbaron: performance tests should run on slow boxes, correctness tests should run as quickly as possible. Dbaron notes that correctness tests, if done possible should take quite a while.
schrep: can see need for three classes of machines: builds, performance, correctness.
schrep: conceivably having a build system analogous to Java+Junit+Ant where a make target could invoke a set of tests and output the results to a text or xml file for Tinderbox to pick up. This allows developers to run tests as well as have them automatically invoked in tinderbox.