Closed Bug 1693134 Opened 4 years ago Closed 3 years ago

on new osx arm64 machines running bigsur, automation fails to run AUS related tests

Categories

(Toolkit :: Application Update, task)

task

Tracking

()

RESOLVED FIXED
Tracking Status
firefox87 --- affected

People

(Reporter: jmaher, Unassigned)

References

Details

here is what tests look like by default:
https://treeherder.mozilla.org/jobs?repo=try&searchStr=test-macosx&revision=d421636d58a6158570ce378885be9e946d8a585c

and here is what tests look like with the lsFilequarantineEnabled flag removed:
https://treeherder.mozilla.org/jobs?repo=try&searchStr=test-macosx&revision=c573eac32d3ec8658ac097e419a42f1325b35554

here is a link to the quarantine flag:
https://searchfox.org/mozilla-central/source/browser/app/macbuild/Contents/Info.plist.in#237

I have experimented unsuccessfully using xattr -c <filename> and various directories without resolving the failing AUS tests.

I don't know much about these tests, there appears to be a lot of file copying and preparation that takes place and it is hard to easily figure out what binaries are being referenced.

I get failures on my local M1 MBP ./mach test toolkit/mozapps/update/tests/unit_aus_update/, there are popups for org.mozilla.updater not being able to run.

Until this is resolved, I don't see a path forward for turning on xpcshell tests and the included AUS tests in automation on bigsur/M1.

Blocks: 1673067

Mike, Haik, are you able to assist here?

Flags: needinfo?(mh+mozilla)
Flags: needinfo?(haftandilian)

Wild guess: you need a signed build. The test is using an unsigned one.

Flags: needinfo?(mh+mozilla)

Also, I see those tests are running the tests against the x86-64 build. Is that really what you want?

I am not aware of another build? What build do our end users get?

as for signing, I would imagine this would be resolved/done on existing 10.14 machines/builds/tests- I am just copying things as best as I can.

macos has more requirements on arm64 for code signing, so code signing-related issues that should up there may not affect intel mac machines.

Depends on: 1693462

I believe this is fixed now. At least, they're working fine in my try push on https://treeherder.mozilla.org/jobs?repo=try&author=bhearsum%40mozilla.com&selectedTaskRun=EJpwWAO7Rw2HLhGwmw6jXA.0, and I expect to be able to enable them on central again next week. The underlying fixes we did in https://bugzilla.mozilla.org/show_bug.cgi?id=1714200 were to run generic-worker & python arm64 binaries (to avoid launching in rosetta), and make sure all tests were using signed builds instead of unsigned ones.

I'm calling this fixed. Please re-open or file a new bug if you think there's something still to address here.

Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(haftandilian)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.