Confirmed users
3,816
edits
QA/TDAI/Mobile Test Framework Meeting: Difference between revisions
Jump to navigation
Jump to search
QA/TDAI/Mobile Test Framework Meeting (view source)
Revision as of 21:54, 29 September 2009
, 29 September 2009→Assignment
(→python) |
|||
| Line 96: | Line 96: | ||
= Assignment = | = Assignment = | ||
* bmoss's team will drive this, working with brad lassey to get this working. | |||
* First step is prove out that this will actually work and that we have reasonable answers to the questions that have been raised. | |||
* If it is acceptable then we can look at rolling it out moving forward. | |||
== mechanical questions == | |||
* what platform try it on first? | |||
** Is there any reason it can't run on one and not the other? No. If it works on winmo then it should be fine on CE. So, go for WinMO first | |||
* Do we stop at the other attempt on talos in the meantime? | |||
** Yes. It would make sense for releng to scale up windows mobile devices for infrastructure/powered/network etc. | |||
** Let all the reporting and software pieces be hammered out by the infrastructure guys. | |||
* Alice and Aki/John should let us know about things that they hit when scaling out talos so taht we can avoid those roadblocks. Most of the strange errors were with buildbot. | |||
** There may not be any need to talk buildbot at all. | |||
** Talos does not generate the builds it tests. It feels like you could still use buildbot on the server side so that it knows when the builds are available. and then the server could take care of moving the builds down to the devices under test. | |||
** Queueing the buildbot notifications on what builds to run what tests/talos on will be something that the server will understand. Ability to resend and retest builds is something that we want to keep up and running, so the new server will integrate with the existing buildbot infrastructure. | |||