1524400 - Run mochitest using generic-worker on windows/aarch64

Status: RESOLVED FIXED

(Testing :: General, task, P3)

Description

[Edwin Takahashi (:egao | infrequent contributor)]

Now that generic-worker has been proven to run on win64/aarch64, make it run the mochitest suite.

Record the outcomes and/or issues that occur.

Comment 1

[Edwin Takahashi (:egao | infrequent contributor)]

Mochitest suite was completed in 6572s.

Result

N5gqeqPYT1OcBx4w0gYVBg

13:43:02     INFO -  0 INFO TEST-START | Shutdown
13:43:02     INFO -  1 INFO Passed:  670029
13:43:02     INFO -  2 INFO Failed:  61
13:43:02     INFO -  3 INFO Todo:    1666
13:43:02     INFO -  4 INFO Mode:    e10s
13:43:02     INFO -  5 INFO SimpleTest FINISHED
13:43:02     INFO - Buffered messages finished
13:43:02     INFO - SUITE-END | took 6572s

Comment 2

[Edwin Takahashi (:egao | infrequent contributor)]

May be coincidental, but observed that my win10/aarch64 reference laptop experienced multiple driver failures.

Events according to Event Viewer, all times in PST:

WARNING 1:43:29PM: shutdown.exe was initiated from generic-worker
WARNING 1:43:29PM: Generic Worker service terminated with network name cannot be found
INFO 1:43:33PM: winlogon
WARNING 1:43:52PM: Kernel-PnP reports multiple instances of failure to load device ACPI\QCOM<hex_identifier>\2%daba3ff&0
ERROR 1:44:31PM: RasMan service failed to start due to SstpSvc failing to start
CRITICAL 1:45:00PM: one or more user-mode driver had issues and process has been terminated.

The shutdown process at 1:43:29PM is normal due to Generic-Worker requesting a reboot after test run concludes. It appears that after the machine boots up and logs into the account, a cascading series of failures occurred on multiple drivers that culminated in loss of network connectivity.

The list of devices that failed according to Device Manager:

• qSarMgr Device
• Qualcomm Service Manager Device
• Qualcomm Subsystem Dependency Device
• Qualcomm Bus Device

Comment 3

[(Away)]

Is this bug only for the plain flavor of mochitest? Or does it also cover mochitest-chrome, mochitest-browser, etc.?

Comment 4

[Edwin Takahashi (:egao | infrequent contributor)]

(In reply to David Major [:dmajor] from comment #3)

Is this bug only for the plain flavor of mochitest? Or does it also cover mochitest-chrome, mochitest-browser, etc.?

I intended this to cover all flavors of mochitest, but that may quickly get out of hand.

=================

In reference to Comment 2, I was able to confirm that my run of mochitest rendered several key pieces of driver inoperable.

The method to restore functionality on the windows/aarch64 laptop is to perform a Windows Refresh > Keep Files. This takes approximately 30 mins to 1 hour and requires reinstallation of generic-worker.

Comment 5

[Edwin Takahashi (:egao | infrequent contributor)]

Treeherder: link

Taskcluster: link

Mochitest run on Bitbar-hosted win10/aarch64 device, from a ./mach try push.