Bug 451812 comment 1 { From Robert Kaiser 2008-08-23 06:44:10 PDT As a followup to that, we could probably kill the platform-specific variants of those steps, as only the syntax/path of the command is different anyway. Note that this is one change I already have made for SeaMonkey from the beginning, so only MoCo users need to get fixed for that. } See </tools/buildbotcustom/unittest/steps.py>.

Removed --appname from the browser chrome test step, I'm assuming it works the same way as the other runtests.py variants. Still need patches for the various buildbot configs that call the removed steps.

Do we need a patch for the 3.0 branch too?

Ran successfully in staging with all patches. Targeting Friday morning downtime for enabling in production.

Comment on attachment 342614 [details] [diff] [review] Remove platform-specific test steps Checking in steps.py; /cvsroot/mozilla/tools/buildbotcustom/unittest/steps.py,v <-- steps.py new revision: 1.17; previous revision: 1.16 done

Comment on attachment 352356 [details] [diff] [review] Remove platform-specific steps from the unittest factory This ran fine in staging. Checking in process/factory.py; /cvsroot/mozilla/tools/buildbotcustom/process/factory.py,v <-- factory.py new revision: 1.56; previous revision: 1.55 done

Comment on attachment 350523 [details] [diff] [review] master.cfg changes changeset: 591:a922c2a6a037

Comment on attachment 350539 [details] [diff] [review] master.cfg patch for 3.0 if needed Checking in master.cfg; /cvsroot/mozilla/tools/buildbot-configs/testing/unittest/master.cfg,v <-- master.cfg new revision: 1.40; previous revision: 1.39 done

Needed one last change to get things working during the downtime this morning. Patch is currently running in production.

Comment on attachment 352754 [details] [diff] [review] Reload modules in unittest master.cfg changeset: 600:f411d0e514f2