ReleaseEngineering/SpecialRepositories: Difference between revisions
Jump to navigation
Jump to search
(Created page with "= Special branches = Release Engineering and the A-Team has various project branches booked permanently for various reasons: * Ash - where we can try mozharness patches withou...") |
m (Update BuildDuty to CiDuty. Renaming project) |
||
| (7 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
= Special branches = | = Special branches = | ||
Release Engineering and the A-Team | Release Engineering and the A-Team have various [[ReleaseEngineering/DisposableProjectBranches#Indefinite_booking|project branches]] booked permanently for various reasons: | ||
* Cedar - where we enable test jobs that are still failing | * Cedar - where we enable test jobs that are still failing | ||
= Cedar = | = Cedar = | ||
| Line 111: | Line 76: | ||
* get review for your change | * get review for your change | ||
* land | * land | ||
* wait for reconfig, or poke | * wait for reconfig, or poke ciduty for an expedited reconfig if needed. | ||
Latest revision as of 08:39, 14 May 2018
Special branches
Release Engineering and the A-Team have various project branches booked permanently for various reasons:
- Cedar - where we enable test jobs that are still failing
Cedar
Merging m-c into Cedar
We can merge the latest m-c code into cedar to:
- compare latest unittest results + talos numbers between m-c buildbot tests and cedar mozharness tests
- get new cedar builds for testing
To do this:
# Get a copy of cedar hg clone http://hg.mozilla.org/projects/cedar cd cedar # Update to latest, in case someone has updated cedar since you last cloned/updated. # the hg up -C will blow away any local changes! hg pull hg up -C -r default # Pull latest m-c changes in hg pull http://hg.mozilla.org/mozilla-central hg merge hg commit -m "Merge m-c -> cedar" # Push to cedar hg push ssh://hg.mozilla.org/projects/cedar
Results will show up here.
Viewing logs
Jobs will show up on tbpl as they finish.
To view logs
- click on the job on the right
- find "View full log" at the bottom left of the page; click
Known issues are filed against the two tracking bugs:
- bug 713055 - roll out mozharness desktop talos to m-c and project branches
- bug 793022 - roll out mozharness desktop unittests to m-c and project branches
If you find new issues, please file a bug blocking one or both bugs.
Retriggering jobs
- Go to tbpl
- Click on the job in question
- The plus sign in the bottom left will retry the job.
Each of these will pull the latest-and-greatest from mozharness, so if you checked a fix in, you can re-run the broken tests.
Adding additional tests to Cedar
If we want to readd tpaint once bug 794587 is fixed:
- add "tpaint" to the other suite tests here: http://hg.mozilla.org/projects/cedar/file/38215d0638b0/testing/talos/talos.json#l55
- check that into ssh://hg.mozilla.org/projects/cedar
- the resulting build will trigger an "other" talos suite with tpaint.
If we want to add another test type, e.g. marionette, to cedar:
- add "cedar" to the list of marionette branches here: http://hg.mozilla.org/build/buildbot-configs/file/680736f2dc1f/mozilla-tests/config.py#l1076
- move the marionette for loop below the unittest for loop.
- This is because the unittest for loop zeros out the tests for cedar here.
- (this is because we don't want to have both buildbot-based and mozharness-based tests running on cedar.)
- This is because the unittest for loop zeros out the tests for cedar here.
- get review for your change
- land
- wait for reconfig, or poke ciduty for an expedited reconfig if needed.