Confirmed users
353
edits
EngineeringProductivity/Projects/Treeherder/Meetings/2013-01-23: Difference between revisions
EngineeringProductivity/Projects/Treeherder/Meetings/2013-01-23 (view source)
Revision as of 23:52, 29 January 2013
, 29 January 2013→Test Objects
| Line 12: | Line 12: | ||
* Test objects should not be limited to data from logs. If you could have raw log, parsed log, and references to binary locations, screen shots, recordings during tests, etc all could be keys inside results dictionary. | * Test objects should not be limited to data from logs. If you could have raw log, parsed log, and references to binary locations, screen shots, recordings during tests, etc all could be keys inside results dictionary. | ||
* Parsed logs would be all the data from the log - python lib that the slaves could use to parse the log before upload but the raw log would also be uploaded as well. | * Parsed logs would be all the data from the log - python lib that the slaves could use to parse the log before upload but the raw log would also be uploaded as well. | ||
** Note: Not sure we need to store the raw log separately, could just store a pointer to it. How does the storage of raw logs currently work? How long do we keep them for? | |||
* Some of the test automation frameworks generate their own summaries and buildbot generates its own summaries on top of that, this should be cleaned up as part of this effort or alongside it. | |||
** This should be done in mozharness not in buildbot | |||
* The build object can have any number of test objects associated with it. | |||
* There are logs outside the tests - the buildbot master log etc. | |||
== Pushlog Objects == | == Pushlog Objects == | ||