CI Automation/windows10 aarch64: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Added section to install)
(how to run tests)
Line 32: Line 32:
Instruction originally from [https://bugzilla.mozilla.org/show_bug.cgi?id=1522997#c2 1522997].
Instruction originally from [https://bugzilla.mozilla.org/show_bug.cgi?id=1522997#c2 1522997].


'''Prerequisites'''
=== Prerequisites ===
* disable Windows S mode
* disable Windows S mode
* disable User Account Control
* disable User Account Control
Line 38: Line 38:
* download NSSM to C:\nssm-2.24\
* download NSSM to C:\nssm-2.24\
* create "Remote Desktop Users" group:
* create "Remote Desktop Users" group:
  * net localgroup "Remote Desktop Users" /add
  net localgroup "Remote Desktop Users" /add
* log in to Taskcluster
* log in to Taskcluster
* request scope `assume:project:taskcluster:generic-worker-tester`  
* request scope `assume:project:taskcluster:generic-worker-tester`  


'''Steps'''
=== Steps ===


# download the current 386 release of `generic-worker-windows-386.exe` from [https://github.com/taskcluster/generic-worker/releases taskcluster generic-worker].
# download the current 386 release of `generic-worker-windows-386.exe` from [https://github.com/taskcluster/generic-worker/releases taskcluster generic-worker].
Line 50: Line 50:
# rename generic-worker-windows-386.exe to generic-worker.exe.
# rename generic-worker-windows-386.exe to generic-worker.exe.
# generate two signing keys:
# generate two signing keys:
  * generic-worker new-openpgp-keypair --file <unique_file_name>
  generic-worker new-openpgp-keypair --file <unique_file_name>
  * generic-worker new-ed25519-keypair --file <unique_file_name>
  generic-worker new-ed25519-keypair --file <unique_file_name>
# create generic-worker.config and include the following:
# create generic-worker.config and include the following:
"accessToken":                "<access token tied to taskcluster>",
"clientId":                  "<client ID tied to taskcluster>",
"ed25519SigningKeyLocation":  "<file location you wrote ed25519 private key in step 6>",
"livelogSecret":              "<any text>",
"openpgpSigningKeyLocation":  "<file location you wrote gpg private key kn step 6>",
"provisionerId":              "test-provisioner",
"publicIP":                  "<ideally an IP address of one of your network interfaces>",
"rootURL":                    "https://taskcluster.net",
"workerGroup":                "test-worker-group",
"workerId":                  "test-worker-id",
"workerType":                "<a unique string that only you will use for your test worker(s)>"
# launch cmd.exe with Administrator rights.
# launch cmd.exe with Administrator rights.
# cd c:\generic-worker
# cd c:\generic-worker
Line 83: Line 94:
* cppunittest
* cppunittest


For an up-to-date definition, 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 =
 
== Overview ==
 
This is probably what you came to the document for. How to run tests against the windows10-aarch64 hardware we currently have running.
 
Follow these steps to be able to enable windows10-aarch64 tests for the try server. These steps are required as of 2019-02-25; it will become obsolete when windows10-aarch64 tests are released to the general public.
 
=== Prerequisites ===
 
* try access
* up-to-date mozilla-central codebase
 
=== Steps ===
 
# open the file at taskcluster/ci/test/test-platforms.yml
# search for 'windows10-aarch64/opt'
# uncomment all or some of the items under 'test-sets'
# make changes to the local codebase that needs testing
# ./mach try fuzzy
# select tests that need to be run
# enter


= Bugs =
= Bugs =


These are the top-level bugs; the recommended view is [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1522997&hide_resolved=0 tree].
These are the top-level tracking bugs; the recommended view is [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1522997&hide_resolved=0 tree] (login required).


<bugzilla>
<bugzilla>

Revision as of 00:35, 26 February 2019

Overview

With the announcement of the Qualcomm-Mozilla partnership came the need to release a version of Firefox for the ARM64 architecture.

Since mid-January 2019 the CI-A team has been working to enable existing test harnesses, continuous integration tests and other tools to run on Windows 10 ARM64.

Information

Hardware

  • Make: Lenovo
  • Model: C630 YOGA
  • Processor: Qualcomm Snapdragon 850 3.0GHz
  • Cores: 8
  • Memory: 8GB
  • Disk: 128GB SSD

Hosting

Currently an array of 9 machines are hosted at Bitbar in the United States.

Setup

Tests that are run against windows10-aarch64 execute using Taskcluster Generic-Worker. These are installed as a service on the Windows 10 ARM64 manually or via OpenCloudConfig.

A brief walkthrough of the steps to have Taskcluster Generic-Worker running on Windows 10 ARM64 will be provided.

Using only generic-worker

Follow this step to install Taskcluster Generic-Worker on the hardware, and have it launch as a service. After following these steps, the hardware should be ready to accept any tasks started on Taskcluster.

Instruction originally from 1522997.

Prerequisites

  • disable Windows S mode
  • disable User Account Control
  • disable Windows Firewall
  • download NSSM to C:\nssm-2.24\
  • create "Remote Desktop Users" group:
net localgroup "Remote Desktop Users" /add
  • log in to Taskcluster
  • request scope `assume:project:taskcluster:generic-worker-tester`

Steps

  1. download the current 386 release of `generic-worker-windows-386.exe` from taskcluster generic-worker.
  2. download the latest 386 version of livelog.exe and taskcluster-proxy.exe.
  3. create new directory C:\generic-worker.
  4. move the three executable files under C:\generic-worker.
  5. rename generic-worker-windows-386.exe to generic-worker.exe.
  6. generate two signing keys:
generic-worker new-openpgp-keypair --file <unique_file_name>
generic-worker new-ed25519-keypair --file <unique_file_name>
  1. create generic-worker.config and include the following:
"accessToken":                "<access token tied to taskcluster>",
"clientId":                   "<client ID tied to taskcluster>",
"ed25519SigningKeyLocation":  "<file location you wrote ed25519 private key in step 6>",
"livelogSecret":              "<any text>",
"openpgpSigningKeyLocation":  "<file location you wrote gpg private key kn step 6>",
"provisionerId":              "test-provisioner",
"publicIP":                   "<ideally an IP address of one of your network interfaces>",
"rootURL":                    "https://taskcluster.net",
"workerGroup":                "test-worker-group",
"workerId":                   "test-worker-id",
"workerType":                 "<a unique string that only you will use for your test worker(s)>"
  1. launch cmd.exe with Administrator rights.
  2. cd c:\generic-worker
  3. generic-worker.exe install service --config generic-worker.config --nssm c:\nssm-2.24\win32\nssm.exe
  4. reboot once installed.
  5. launch cmd.exe with Administrator rights.
  6. sc query "Generic Worker"

Using OpenCloudConfig

This is the method that is used in production.

Steps originally taken from 1520432.

  1. Invoke-Expression (New-Object Net.WebClient).DownloadString('https://raw.githubusercontent.com/mozilla-releng/OpenCloudConfig/aarch64/userdata/rundsc.ps1')

Currently Running

Currently supported list of tests include:

  • awsy
  • mochitest (all flavors, including e10s)
  • web-platform-tests (all flavors)
  • reftests

Supported, requires non-artifact build:

  • jittest
  • gtests
  • cppunittest

For an up-to-date list of tests, please refer to this file.

Run tests

Overview

This is probably what you came to the document for. How to run tests against the windows10-aarch64 hardware we currently have running.

Follow these steps to be able to enable windows10-aarch64 tests for the try server. These steps are required as of 2019-02-25; it will become obsolete when windows10-aarch64 tests are released to the general public.

Prerequisites

  • try access
  • up-to-date mozilla-central codebase

Steps

  1. open the file at taskcluster/ci/test/test-platforms.yml
  2. search for 'windows10-aarch64/opt'
  3. uncomment all or some of the items under 'test-sets'
  4. make changes to the local codebase that needs testing
  5. ./mach try fuzzy
  6. select tests that need to be run
  7. enter

Bugs

These are the top-level tracking bugs; the recommended view is tree (login required).

Full Query
ID Summary Priority Status
1520867 Investigate running tests on Windows / arm64 P1 RESOLVED
1523722 Run gtest using generic-worker on Windows/aarch64 P3 RESOLVED
1524114 Run xpcshell-test using generic-worker on Windows/aarch64 P3 RESOLVED
1524400 Run mochitest using generic-worker on windows/aarch64 P3 RESOLVED
1524410 Run reftest suites using generic-worker on windows/aarch64 P3 RESOLVED
1525118 [meta] Run taskcluster task from mach try on Bitbar -- RESOLVED
1525434 Run web-platform-test suite using generic-worker on windows/aarch64 P3 RESOLVED
1526015 Run cppunit, jittest, marionette using generic-worker on Windows/aarch64 P3 RESOLVED
1527177 Intermittent [taskcluster:error] [mounts] reading file in zip archive: file already exists: Z:\task_1549919043\mozharness\LICENSE P5 RESOLVED
1527469 Enable windows10-aarch64 build and tests on try server -- RESOLVED
1530737 unable to run talos/raptor on win/aarch64 builds in CI -- RESOLVED
1531876 run talos/raptor tests on windows10 aarch64 laptops P1 RESOLVED
1531878 [taskcluster:error] [mounts] reading file in zip archive: file already exists: C:\tasks\task_1551392763\mozharness\LICENSE P1 RESOLVED
1531927 [meta] windows/aarch64 - skipped/disabled media tests P5 RESOLVED
1533114 [meta] windows/aarch64 - skipped/disabled a11y tests P5 NEW
1533880 [meta] windows/aarch64 - skipped/disabled web-platform-tests P5 NEW
1534823 [meta] windows/aarch64 - skipped/disabled mochitest tests P5 NEW
1535467 windows/aarch64 - test screenshots sometimes show "Windows Defender Firewall has blocked some features of this app" P3 NEW
1536208 [meta] windows/aarch64 - skipped/disabled xpcshell tests P5 RESOLVED
1536283 [meta] windows/aarch64 - skipped/disabled marionette tests P5 RESOLVED
1536354 [meta] windows/aarch64 - skipped/disabled reftests P5 NEW
1538785 windows/aarch64 - plugin tests failing on windows10-aarch64 -- RESOLVED
1539693 windows/aarch64 - re-enable/adjust web-platform-tests results based on new timeout multiplier -- RESOLVED
1540213 windows/aarch64 - enable tests for windows10-aarch64 on taskgraph -- RESOLVED
1543521 windows/aarch64 - lower windows10-aarch64 to tier 2 on try -- RESOLVED
1545810 windows/aarch64 - web platform test chunk investigation -- RESOLVED
1546532 windows/aarch64 - enable mochitest-a11y -- RESOLVED
1546728 windows/aarch64 - enable cppunit -- RESOLVED
1546732 windows/aarch64 - enable jittest -- RESOLVED
1547820 windows/aarch64 - testing/web-platform/tests/media-source crashes on ARM64 -- RESOLVED
1552051 windows/aarch64 - run SM(p) instead of jittest P2 RESOLVED
1572185 Re-enable CSS web-platorm-tests for windows10-aarch64 -- RESOLVED

32 Total; 5 Open (15.63%); 27 Resolved (84.38%); 0 Verified (0%);

Retrieved from "https://wiki.allizom.org/index.php?title=CI_Automation/windows10_aarch64&oldid=1208125"