CI Automation/windows10 aarch64: Difference between revisions

Jump to navigation Jump to search
Merged 'Running tests Locally' with new section on setup
(Some minor updates)
(Merged 'Running tests Locally' with new section on setup)
Line 33: Line 33:


# place the script in the mozilla-build directory
# place the script in the mozilla-build directory
# copy the task ID from treeherder for the Build
# copy the task ID from treeherder for the windows10-aarch64 Build (artifact is supported)
# invoke start-shell.bat, which will launch a bash-like command line
# invoke start-shell.bat, which will launch a bash-like command line
# from mozilla-build directory, run the test runner script as follows:
# from mozilla-build directory, run the test runner script as follows:
  bash script.sh task_id test_type <chunk_to_run> <total_chunks>
  bash script.sh task_id test_type <chunk_to_run> <total_chunks>
Example:
bash script.sh Q-CE8DFvSAWmc08vw6bd6A xpcshell 1 8


=== Mozilla-central ===
=== Mozilla-central ===
Line 132: Line 135:


For an up-to-date list of tests, please refer to [https://searchfox.org/mozilla-central/source/taskcluster/ci/test/test-platforms.yml#222 this file].
For an up-to-date list of tests, please refer to [https://searchfox.org/mozilla-central/source/taskcluster/ci/test/test-platforms.yml#222 this file].
= Run tests Locally =
Theoretically, you can run tests locally with mach from a local build environment. However, since our aarch64 builds are usually cross-compiled in an x86 environment, you probably don't have a local build environment!
The recommended alternative is to use mozharness to download, install, and test a build from try or continuous integration. A handy script is provided as an attachment to {{bug|1520867}} that greatly simplifies running tests from mozharness; let's call that script 'moztest'.
Run moztest from a MozillaBuild shell. You need only a few parameters:
* The task-id of the Windows-aarch64 build that you want to test: Click on the aarch64 build in treeherder, and copy the "Task" shown in the treeherder detail pane; it might look like "Q-CE8DFvSAWmc08vw6bd6A".
* The name of the test suite you want to run: one of (cppunit, gtest, xpcshell, mochitest, mochitest-chrome, mochitest-clipboard, mochitest-dt, mochitest-gpu, mochitest-media, crashtest, jsreftest, reftest, jittest, web-platform, web-platform-reftest, web-platform-wdspec, raptor-speedometer, raptor-tp6, talos-g5, talos-chromez)
* Optionally, the test "chunk" number to run and the number of test chunks to split the suite into.
For example:
* moztest Q-CE8DFvSAWmc08vw6bd6A cppunit
* moztest Q-CE8DFvSAWmc08vw6bd6A xpcshell 1 3


= Run tests on Try =
= Run tests on Try =
75

edits

Navigation menu