Tinderbox/Modules: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 1: | Line 1: | ||
Tinderbox organizes measurements, fixture setup, and fixture teardown into groups called ''modules'' |
Tinderbox organizes measurements, fixture setup, and fixture teardown into groups called ''modules''. |
||
⚫ | |||
* Modules are implemented as python modules such as [http://dev.laptop.org/git?p=projects/tinderbox;a=blob;f=jhbuild/modtypes/olpc.py;hb=HEAD jhbuild.modtypes.olpc]. |
|||
* Tinderbox learns about modules by reading XML descriptors called "modulesets". Example modulesets include the [http://dev.laptop.org/git?p=sugar-jhbuild;a=blob_plain;f=config/modulesets/platform.modules;hb=HEAD jhbuild modules] and the [http://dev.laptop.org/git?p=projects/tinderbox;a=blob;f=modulesets/olpc.modules;hb=HEAD "olpc" moduleset]. |
|||
Modules are further subdivided into phases. |
Modules are further subdivided into phases. |
||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ |
Latest revision as of 01:05, 26 April 2008
Tinderbox organizes measurements, fixture setup, and fixture teardown into groups called modules.
- Module source code is located in Tinderbox's jhbuild.modtypes python package.
- Modules are implemented as python modules such as jhbuild.modtypes.olpc.
- Tinderbox learns about modules by reading XML descriptors called "modulesets". Example modulesets include the jhbuild modules and the "olpc" moduleset.
Modules are further subdivided into phases.
- Sugar-jhbuild modules have phases such as "start", "checkout", "build", "install".
- The "olpc" module has phases including "start", "download", "nandwrite", "boot", "networking", "sugar", "activities", "performance", and "reboot".
- The phases are implemented as named functions inside Tinderbox python modules, e.g. the "olpc" module's "start" phase is the "do_start(...)" function in jhbuild.modtypes.olpc.