[Tracking Requested - why for this release]:

• central-as-beta simulation
• How to run these simulations

Failure logs

• service-workers/service-worker/update-module-request-mode.https.html | headers of a main module script - assert_equals: expected (string) "same-origin" but got (undefined) undefined: https://treeherder.mozilla.org/logviewer?job_id=336798457&repo=try
• html/cross-origin-embedder-policy/reporting-navigation.https.html | parent: |header(cross-origin-embedder-policy,require-corp), target: |header(cross-origin-resource-policy,cross-origin)|header(content-security-policy,frame-ancestors 'none'), with empty frame: false - global.ReportingObserver is not a constructor: https://treeherder.mozilla.org/logviewer?job_id=336798511&repo=try
• TEST-UNEXPECTED-TIMEOUT | /html/cross-origin-embedder-policy/multi-globals/workers-coep-report.https.html | Multiple globals for Worker constructor: COEP reports - Test timed out https://treeherder.mozilla.org/logviewer?job_id=336798518&repo=try

The failure depend on different preference, hence the issues will get tracked by different bugs.

update-module-request-mode.https.html depends on Sec-Fetch which is only enabled
in Nightly (behind preference dom.security.secFetch.enabled added bug 1508292).
Shipping Sec-Fetch-* is tracked by bug 1695911. The test got added in
bug 1702610.

There were no occurrences in today's beta-sim after importing the patch.

https://hg.mozilla.org/releases/mozilla-beta/rev/db228f66e054

https://hg.mozilla.org/mozilla-central/rev/3bf84ddb02e2