947
edits
Auto-tools/Projects/Mozmill/Meeting 2010 09 28: Difference between revisions
Auto-tools/Projects/Mozmill/Meeting 2010 09 28 (view source)
Revision as of 20:34, 28 September 2010
, 28 September 2010→Mozmill + Buildbot Woes and 1.5.1: no external images :(
m (→Mozmill + Buildbot Woes and 1.5.1: note degree of sadness) |
m (→Mozmill + Buildbot Woes and 1.5.1: no external images :() |
||
| Line 3: | Line 3: | ||
* Method 1: Use a different windows API call to create the process. This might work. Experimenting now with this approach. It is the "more correct" way, and the smaller change to mozrunner. | * Method 1: Use a different windows API call to create the process. This might work. Experimenting now with this approach. It is the "more correct" way, and the smaller change to mozrunner. | ||
* Method 2: Punt on the issue. We can take the code from automation.py.in that the rest of the harnesses use and we can manage the processes that way. We will likely be revisiting this code once we switch to E10S across the board, but we will have to do that for the other test harnesses too. This has a large impact on the existing code in mozrunner, though it does overall make the code much simpler to write/read/maintain. | * Method 2: Punt on the issue. We can take the code from automation.py.in that the rest of the harnesses use and we can manage the processes that way. We will likely be revisiting this code once we switch to E10S across the board, but we will have to do that for the other test harnesses too. This has a large impact on the existing code in mozrunner, though it does overall make the code much simpler to write/read/maintain. | ||
= Timeline = | = Timeline = | ||