Bugzilla

This has been happening for a while now but it's been hiding under meta Bug 1809667. 
Unfortunately an increase in number of chunks from 16->20 for that platform won't work this time around as seen in this [try push](https://treeherder.mozilla.org/jobs?repo=try&group_state=expanded&resultStatus=success%2Cpending%2Crunning%2Ctestfailed%2Cbusted%2Cexception&classifiedState=unclassified&revision=5b24d67ccede8631369b0e7ff8ef84a11dc7ccac&searchStr=wpt11&selectedTaskRun=T5vc0rFtQGeV9vqpeTUtPA.0). wpt11 runs are borderline to the max run time with them being around 118-120 mins. 

Before this happening again (because it happened also in Bug 1821918) these runs were around 112-116 mins long as seen in [this range](https://treeherder.mozilla.org/jobs?repo=mozilla-central&resultStatus=testfailed%2Cbusted%2Cexception%2Csuccess%2Crunning%2Cpending%2Crunnable&searchStr=win%2Cwpt3&tochange=36ce680ea81ccb2f123f0f6831596185e6ea4e83&fromchange=87846ae3f12d74bcc97619bea65453ce0aca0e54&selectedTaskRun=cSRCPlYfS-qryGKZHJKRCw.0).  Something in [this merge](https://hg.mozilla.org/mozilla-central/pushloghtml?changeset=36ce680ea81ccb2f123f0f6831596185e6ea4e83) made them run overboard. 

The common manifests between those two chunk iterations are:
```
    /IndexedDB
    /media-source/dedicated-worker
    /pointerevents
    /shadow-dom/focus
    /uievents/legacy
    /upgrade-insecure-requests/gen
    /webaudio/the-audio-api/the-channelmergernode-interface
    /webxr/dom-overlay
```
So some tests in these manifests are taking longer than usual to complete and make the task run near the max run time.

This has been happening for a while now but it's been hiding under meta Bug 1809667. 
Unfortunately an increase in number of chunks from 16->20 for that platform won't work this time around as seen in this [try push](https://treeherder.mozilla.org/jobs?repo=try&group_state=expanded&resultStatus=success%2Cpending%2Crunning%2Ctestfailed%2Cbusted%2Cexception&revision=5b24d67ccede8631369b0e7ff8ef84a11dc7ccac&searchStr=wpt11&selectedTaskRun=T5vc0rFtQGeV9vqpeTUtPA.0). wpt11 runs are borderline to the max run time with them being around 118-120 mins. 

Before this happening again (because it happened also in Bug 1821918) these runs were around 112-116 mins long as seen in [this range](https://treeherder.mozilla.org/jobs?repo=mozilla-central&resultStatus=testfailed%2Cbusted%2Cexception%2Csuccess%2Crunning%2Cpending%2Crunnable&searchStr=win%2Cwpt3&tochange=36ce680ea81ccb2f123f0f6831596185e6ea4e83&fromchange=87846ae3f12d74bcc97619bea65453ce0aca0e54&selectedTaskRun=cSRCPlYfS-qryGKZHJKRCw.0).  Something in [this merge](https://hg.mozilla.org/mozilla-central/pushloghtml?changeset=36ce680ea81ccb2f123f0f6831596185e6ea4e83) made them run overboard. 

The common manifests between those two chunk iterations are:
```
    /IndexedDB
    /media-source/dedicated-worker
    /pointerevents
    /shadow-dom/focus
    /uievents/legacy
    /upgrade-insecure-requests/gen
    /webaudio/the-audio-api/the-channelmergernode-interface
    /webxr/dom-overlay
```
When comparing the manifests from the green runs before those central changes and the ones from the max run time I get the same above list of manifests. So adding these ones was what made them run overboard. 
I don't understand why these won't chunk when increasing from 16 to 20 chunks.