New test environments: Difference between revisions

Jump to navigation Jump to search
Add greening up section
(Add greening up section)
Line 11: Line 11:
= Task Overview =
= Task Overview =


Broadly speaking, the following are the discrete phases involved.
Broadly speaking, the following discrete phases are involved when adding new platforms.


* ensure availability of machines (if hardware)
* ensure availability of machines (if hardware)
 
** responsibility: release engineering
    responsibility: release engineering
      
      
* enable platform on try
* enable platform on try


Line 210: Line 208:


Using <code>./mach try fuzzy --no-artifact</code>, push tests belonging to the new platform to the Tryserver. Do not use artifact builds for the baseline push as some test results (outside of the compiled tests such as <code>cppunit</code>) are affected by the artifact build.
Using <code>./mach try fuzzy --no-artifact</code>, push tests belonging to the new platform to the Tryserver. Do not use artifact builds for the baseline push as some test results (outside of the compiled tests such as <code>cppunit</code>) are affected by the artifact build.
Once the checklist is complete, create a diff on Phabricator and have it reviewed by:
* jmaher
* egao
and any other reviewers as necessary.


=== Example ===
=== Example ===
Line 222: Line 226:
* which tests pass?
* which tests pass?
* which tests fail?
* which tests fail?
* has patch been reviewed and landed to mozilla-central?
= Green up tests =
Once the build and tests are running on Tryserver, it is time to begin greening the tests.\
75

edits

Navigation menu