1884982 - browser-blocking tests are taking too long to run in debug mode, investigate and re-enable

Status: REOPENED

(Core :: Privacy: Anti-Tracking, defect, P3)

Comment 1

[Joel Maher ( :jmaher ) (UTC -8)]

runtime is in the 20 minutes for debug. for 17 tests, that is a bit too much. The outliers are (3 minutes each on windows):
browser_blockingSessionStorage.js
browser_blockingSharedWorkers.js

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

Attachment: Bug 1884982 - disable toolkit/components/antitracking/test/browser/browser-blocking on debug due to extremely long runtime. r=aryx

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/72f2d6b322a3
disable toolkit/components/antitracking/test/browser/browser-blocking on debug due to extremely long runtime. r=aryx,anti-tracking-reviewers,timhuang

Comment 4

[Natalia Csoregi [:nataliaCs]]

https://hg.mozilla.org/mozilla-central/rev/72f2d6b322a3

Comment 5

[Joel Maher ( :jmaher ) (UTC -8)]

Attachment: Bug 1884982 - disable rest of anti tracking browser test cases on debug for 25-40 minute runtimes. r=aryx

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/c5e567a16b9b
disable rest of anti tracking browser test cases on debug for 25-40 minute runtimes. r=aryx,anti-tracking-reviewers,timhuang

Comment 7

[Joel Maher ( :jmaher ) (UTC -8)]

some options to consider:

1. run fewer tests- maybe there are tests that are very similar- cutting the number of tests in half could look better
2. maybe this is important on a single platform and that might be a compromise- if we do re-enable, I would like these to be in <20 minute groupings on debug, so that would mean splitting up the manifest into multiple parts.

Comment 8

[Narcis Beleuzu [:NarcisB]]

https://hg.mozilla.org/mozilla-central/rev/c5e567a16b9b