Central as beta: https://treeherder.mozilla.org/#/jobs?repo=try&resultStatus=testfailed%2Cbusted%2Cexception%2Crunnable&revision=0fdc8b3d856f3abc380e354faa7fbb15fe0ec09c&selectedJob=214380898 Failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=214380898&repo=try Bob, this is a perma failure from today's version bump simulation. Can you please take a look at this? Thank you!

There are a 4 perma Android Jittest failures 1. jit-test/tests/wasm/spec/float_memory.wast.js | #1 module successfully instantiated: PASS. (code 3, args "") [0.3 s] Log link: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=214380898&repo=try&lineNumber=12089 2. jit-test/tests/bug828119.js - exception output: Assertion failed: bad label: 2 Log link: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=214389569&repo=try&lineNumber=1949 3. jit-test/tests/wasm/atomic.js | uncaught exception: out of memory (code 3, args "") [0.4 s] Log link: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=214389446&repo=try&lineNumber=7837 4. jit-test/tests/self-test/assertRecoveredOnBailout-1.js | Segmentation fault (code 139, args "--ion-eager --ion-offthread-compile=off") [0.3 s] Log link: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=214389568&repo=try&lineNumber=6273

That particular error is just one of many but it also appears to be one that already is seen on try. The jit1 failures are different however from recent try experience which have been green. The jittests on android-hw have been disabled on all trunk repos with the exception of try. They remain enabled on beta only due to the fact that I didn't consider it worthwhile to uplift the patch which disabled them. I think this is a false positive that is due to the fact that the jittests on android-hw are configured to run on project try. When we merge central to beta, the jit tests should be also disabled on beta and this will be a non-issue.