Open Bug 1549723 Opened 5 years ago Updated 3 months ago

Enable the startup mainthread IO mochitests on debug builds

Categories

(Core :: Performance, task, P3)

task

Tracking

()

Performance Impact none

People

(Reporter: florian, Unassigned)

References

(Depends on 2 open bugs)

Details

Attachments

(1 file)

Until bug 1529125 lands, we can't enable mainthread IO startup mochitests on debug builds, but I would like to land them anyway and then them only on opt builds for now to already have some main thread I/O coverage.

Depends on: 1529125
Depends on: 1549729
Keywords: leave-open
Pushed by fqueze@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/72723e7257b1
disable browser_startup_mainthreadio.js and browser_startup_content_mainthreadio.js mochitests for debug builds, r=mconley.
Pushed by fqueze@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d81d08e2b3a1
disable browser_startup_mainthreadio.js and browser_startup_content_mainthreadio.js mochitests for debug builds, r=mconley.
Regressions: 1550769

Florian, could you please give this bug a priority? I'll give it a P3 for now since it hasn't been commented on in a while, but please update as necessary.

Priority: -- → P3

The leave-open keyword is there and there is no activity for 6 months.
:Dolske, maybe it's time to close this bug?

Flags: needinfo?(dolske)

This bug is still valid, unfortunately.

Flags: needinfo?(dolske)
Keywords: leave-open
Whiteboard: [fxperf]

Looks like this won't be actionable until we fix bug 1529125 though...

Whiteboard: [fxperf] → [fxperf:p3]
Component: General → Performance
Product: Firefox → Testing

Kelly, it's unclear why this was moved to Testing :: Performance. Maybe you were looking for Core :: Performance if this is a Firefox performance issue?

Flags: needinfo?(kcochrane)

Hey sparky, this is related to an automated test for Firefox that tests main-thread IO, so we thought that Testing :: Performance sounded like the right fit.

Flags: needinfo?(kcochrane)

Hi :mconley, ok I think it might make more sense to have this either in the component for the suite it runs in (Testing :: Mochitest), or the component of the code in question (browser/base/content/test/). Would you know who owns these tests? Maybe they'd have a preference.

Flags: needinfo?(mconley)

Unfortunately, browser/base/content/test doesn't have a great component. Rethinking this, let's move it to Core :: Performance, given that it was florian that was working on this.

Flags: needinfo?(mconley)
Product: Testing → Core

Perfect, thanks!

Performance Impact: --- → none
Severity: normal → S3
Whiteboard: [fxperf:p3]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: