Bug 1525118 Comment 2 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Previous run was building a win64/x86_64 image and using that on the win10/aarch64 hardware in an attempt to run xpcshell.

This obviously led to errors.

A newer run: [efMBjsn0Q66A2tvOdHEHDw](https://tools.taskcluster.net/groups/efMBjsn0Q66A2tvOdHEHDw) has been scheduled.

`xpcshell` has been confirmed to run successfully on the win10/aarch64 hardware, pushed through Taskcluster to the generic-worker. See `test-windows10-aarch64/opt-xpcshell-1`
Previous run was building a win64/x86_64 image and using that on the win10/aarch64 hardware in an attempt to run xpcshell.

This obviously led to errors.

A newer run: [efMBjsn0Q66A2tvOdHEHDw](https://tools.taskcluster.net/groups/efMBjsn0Q66A2tvOdHEHDw) has been scheduled.

`xpcshell` has been confirmed to run successfully on the win10/aarch64 hardware, pushed through Taskcluster to the generic-worker. See `test-windows10-aarch64/opt-xpcshell-1`

Changes that were required to support this run as done by `jmaher`:

https://hg.mozilla.org/try/rev/fb161d0cd20f46a2558cef0d75cb2185c903f3ed
Previous run was building a win64/x86_64 image and using that on the win10/aarch64 hardware in an attempt to run xpcshell.

This obviously led to errors.

A newer run: [efMBjsn0Q66A2tvOdHEHDw](https://tools.taskcluster.net/groups/efMBjsn0Q66A2tvOdHEHDw) has been scheduled.

`xpcshell` has been confirmed to run successfully on the win10/aarch64 hardware, pushed through Taskcluster to the generic-worker. See `test-windows10-aarch64/opt-xpcshell-1`

Changes that were required to support this run as done by `jmaher`: https://hg.mozilla.org/try/rev/fb161d0cd20f46a2558cef0d75cb2185c903f3ed

Back to Bug 1525118 Comment 2