Filed by: ccozmuta [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=354672883&repo=mozilla-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Cydu9_4eRUen0Nrp-2tVug/runs/0/artifacts/public/logs/live_backing.log

[task 2021-10-13T18:19:24.574Z] 18:19:24     INFO - TEST-PASS | devtools/shared/test-helpers/browser_allocation_tracker.js | We got some random number of objects without an allocation site - 
[task 2021-10-13T18:19:24.574Z] 18:19:24     INFO - TEST-PASS | devtools/shared/test-helpers/browser_allocation_tracker.js | All the expected objects were reported freed in the count with allocation sites - 
[task 2021-10-13T18:19:24.574Z] 18:19:24     INFO - TEST-PASS | devtools/shared/test-helpers/browser_allocation_tracker.js | And we released some random number of objects without an allocation site - 
[task 2021-10-13T18:19:24.574Z] 18:19:24     INFO - Leaving test bound 
[task 2021-10-13T18:19:24.574Z] 18:19:24     INFO - Entering test bound 
[task 2021-10-13T18:19:24.574Z] 18:19:24     INFO - TEST-PASS | devtools/shared/test-helpers/browser_allocation_tracker.js | The two objects are reported - 
[task 2021-10-13T18:19:24.575Z] 18:19:24     INFO - Free the transient object
[task 2021-10-13T18:19:24.575Z] 18:19:24     INFO - TEST-PASS | devtools/shared/test-helpers/browser_allocation_tracker.js | We now only have the leaked object - 
[task 2021-10-13T18:19:24.575Z] 18:19:24     INFO - Leaving test bound 
[task 2021-10-13T18:19:24.575Z] 18:19:24     INFO - Entering test bound 
[task 2021-10-13T18:19:24.575Z] 18:19:24     INFO - Test start and stop recording without any debug mode
[task 2021-10-13T18:19:24.576Z] 18:19:24     INFO - Buffered messages logged at 18:18:49
[task 2021-10-13T18:19:24.576Z] 18:19:24     INFO - Leaving test bound 
[task 2021-10-13T18:19:24.576Z] 18:19:24     INFO - Entering test bound 
[task 2021-10-13T18:19:24.577Z] 18:19:24     INFO - Test start and stop recording with 'allocations' debug mode
[task 2021-10-13T18:19:24.577Z] 18:19:24     INFO - Buffered messages logged at 18:18:58
[task 2021-10-13T18:19:24.578Z] 18:19:24     INFO - Leaving test bound 
[task 2021-10-13T18:19:24.578Z] 18:19:24     INFO - Entering test bound 
[task 2021-10-13T18:19:24.579Z] 18:19:24     INFO - Test start and stop recording with 'leaks' debug mode
[task 2021-10-13T18:19:24.580Z] 18:19:24     INFO - Buffered messages logged at 18:19:07
[task 2021-10-13T18:19:24.580Z] 18:19:24     INFO - Leaving test bound 
[task 2021-10-13T18:19:24.580Z] 18:19:24     INFO - Entering test bound 
[task 2021-10-13T18:19:24.580Z] 18:19:24     INFO - Test start and stop recording with tracked objects
[task 2021-10-13T18:19:24.580Z] 18:19:24     INFO - Buffered messages logged at 18:19:15
[task 2021-10-13T18:19:24.581Z] 18:19:24     INFO - Leaving test bound 
[task 2021-10-13T18:19:24.581Z] 18:19:24     INFO - Entering test bound 
[task 2021-10-13T18:19:24.581Z] 18:19:24     INFO - Test start and stop recording with tracked objects
[task 2021-10-13T18:19:24.581Z] 18:19:24     INFO - Buffered messages logged at 18:19:24
[task 2021-10-13T18:19:24.582Z] 18:19:24     INFO - TEST-PASS | devtools/shared/test-helpers/browser_allocation_tracker.js | We get only one leaked objects, the foo object of the sandbox. - 
[task 2021-10-13T18:19:24.584Z] 18:19:24     INFO - TEST-PASS | devtools/shared/test-helpers/browser_allocation_tracker.js | We get an handful of objects without stacks. Most likely created by Memory API itself. - 
[task 2021-10-13T18:19:24.584Z] 18:19:24     INFO - TEST-PASS | devtools/shared/test-helpers/browser_allocation_tracker.js | We get the one leak and the objects with missing stacks - 
[task 2021-10-13T18:19:24.585Z] 18:19:24     INFO - TEST-PASS | devtools/shared/test-helpers/browser_allocation_tracker.js | First item is the objects with missing stacks - 
[task 2021-10-13T18:19:24.585Z] 18:19:24     INFO - Buffered messages finished
[task 2021-10-13T18:19:24.585Z] 18:19:24     INFO - TEST-UNEXPECTED-FAIL | devtools/shared/test-helpers/browser_allocation_tracker.js | For now, the leak report intermittently assume there is less leaked objects than the summary - 
[task 2021-10-13T18:19:24.585Z] 18:19:24     INFO - Stack trace:
[task 2021-10-13T18:19:24.585Z] 18:19:24     INFO - chrome://mochikit/content/browser-test.js:test_ok:1336
[task 2021-10-13T18:19:24.585Z] 18:19:24     INFO - chrome://mochitests/content/browser/devtools/shared/test-helpers/browser_allocation_tracker.js:null:193
[task 2021-10-13T18:19:24.585Z] 18:19:24     INFO - TEST-PASS | devtools/shared/test-helpers/browser_allocation_tracker.js | Second item if about our 'foo' leak - 
[task 2021-10-13T18:19:24.585Z] 18:19:24     INFO - TEST-PASS | devtools/shared/test-helpers/browser_allocation_tracker.js | We leak one object on this file - 
[task 2021-10-13T18:19:24.586Z] 18:19:24     INFO - TEST-PASS | devtools/shared/test-helpers/browser_allocation_tracker.js | We leak from only one line - 
[task 2021-10-13T18:19:24.586Z] 18:19:24     INFO - TEST-PASS | devtools/shared/test-helpers/browser_allocation_tracker.js | On first line, we leak one object - 

Can you please take a look over : https://treeherder.mozilla.org/jobs?repo=mozilla-central&resultStatus=testfailed%2Cbusted%2Cexception%2Crunnable&selectedTaskRun=Cydu9_4eRUen0Nrp-2tVug.0&searchStr=Linux%2C18.04%2Cx64%2CCCov%2CWebRender%2Copt%2CMochitests%2Cwith%2Cfission%2Cenabled%2Ctest-linux1804-64-ccov-qr%2Fopt-mochitest-devtools-chrome-fis-e10s%2Cdt2 ?

Set release status flags based on info from the regressing bug 1539502

https://hg.mozilla.org/mozilla-central/rev/644b1dd9a9fd