Run mochitest using generic-worker on windows/aarch64

RESOLVED FIXED

Status

task
P3
normal
RESOLVED FIXED
7 months ago
4 months ago

People

(Reporter: egao, Assigned: egao)

Tracking

(Depends on 42 bugs)

Firefox Tracking Flags

(Not tracked)

Details

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.

Summary: Run xpcshell-test using generic-worker on aarch64 → Run mochitest using generic-worker on aarch64

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
Summary: Run mochitest using generic-worker on aarch64 → Run mochitest using generic-worker on windows/aarch64

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

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

(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.

Blocks: 1525118
No longer blocks: 1525118

Treeherder: link

Taskcluster: link

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

Depends on: 1525651
Depends on: 1525653
Depends on: 1525657
Depends on: 1525665
Depends on: 1525667
Depends on: 1525668
Depends on: 1525670
Depends on: 1525671
Depends on: 1525678
Depends on: 1525742
Depends on: 1525743
Depends on: 1525749
Depends on: 1525750
Depends on: 1525751
Depends on: 1525752
Depends on: 1525754
Depends on: 1525773
Depends on: 1526064
Depends on: 1526080
Depends on: 1526109
Depends on: 1526430
Depends on: 1526437
Depends on: 1526464
Depends on: 1526539
Depends on: 1526549
Depends on: 1529179
Priority: -- → P3
Depends on: 1412401
Depends on: 1530894
Depends on: 1530895
Depends on: 1531150
Depends on: 1531194
Depends on: 1531484
Depends on: 1531571
Depends on: 1531572
Depends on: 1531573
Depends on: 1531574
Depends on: 1531584
Depends on: 1531586
Depends on: 1531590
Depends on: 1531598
Depends on: 1531603
Depends on: 1531851
No longer depends on: 1412401
Depends on: 1532775
Depends on: 1532778
Depends on: 1532796
Depends on: 1532799
Depends on: 1532817
Depends on: 1532818
Depends on: 1532820
Depends on: 1532830
Depends on: 1533141
Depends on: 1533161
Depends on: 1533162
Depends on: 1533164
Depends on: 1533180
Depends on: 1533184
Depends on: 1533484
Depends on: 1533487
Depends on: 1533490
Depends on: 1533492
Depends on: 1533507
Depends on: 1533529
Depends on: 1533534
Depends on: 1533556
Depends on: 1533814
Depends on: 1533819
Depends on: 1533820
No longer depends on: 1533820
Depends on: 1534811
Depends on: 1534816
Depends on: 1534855
Depends on: 1534857
Depends on: 1534858
Depends on: 1535082
Depends on: 1535140
Depends on: 1535461
Depends on: 1535698
Depends on: 1535775
Depends on: 1535784
Depends on: 1536188
Depends on: 1536347
Depends on: 1536350
Depends on: 1480314
Depends on: 1536564
Depends on: 1536601
No longer depends on: 1535784
Depends on: 1537567
Depends on: 1537592
Depends on: 1537593
Depends on: 1537618
Depends on: 1537620
Depends on: 1537624
Depends on: 1538331
Depends on: 1538359
Depends on: 1538360
Depends on: 1538363
Depends on: 1538391
Depends on: 1538440
Depends on: 1539522
Depends on: 1539546
Depends on: 1539949
Depends on: 1539950
No longer depends on: 1537593
No longer depends on: 1537592
No longer depends on: 1537624
Depends on: 1540837
Depends on: 1541241
Depends on: 1541243
Status: ASSIGNED → RESOLVED
Type: defect → task
Closed: 4 months ago
OS: Unspecified → Windows
Hardware: Unspecified → ARM64
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.