Closed Bug 1576235 Opened 1 year ago Closed 5 months ago

Run macOS tests on integration branches

Categories

(Testing :: Talos, task, P1)

Version 3
task

Tracking

(firefox71 fixed)

RESOLVED FIXED
mozilla71
Tracking Status
firefox71 --- fixed

People

(Reporter: mstange, Assigned: Bebe)

Details

Attachments

(1 file)

Can we start monitoring tresize on macOS for regressions? It seems like a very reliable and stable test that should hardly ever produce false alerts.

I can see four regressions in the graph for the last year and I don't think we have a bug filed on any of them.

Priority: -- → P1

The tresize test isn't the only one that's not running on integration branches and therefore not generating regression alerts. I suspect this was either a capacity concern, or an oversight.

jmaher/fubar: Do you recall any such capacity concerns? If not, then let's review all tests for macOS and enable them on these branches so that we can sheriff them. (I can't currently needinfo jmaher)

Flags: needinfo?(klibby)
Summary: No regression alerts for macOS tresize tests → Run macOS tests on integration branches

I have no recollection, sorry.

Flags: needinfo?(klibby)

I added the tresize suite to run trunk for the mac builds...

If we need to add any other platforms and tests please specify

Flags: needinfo?(mstange)
Flags: needinfo?(dave.hunt)

Apologies for not being more explicit, but I removed 'tresize' from the summary and mentioned in comment 1 that we should review all tests. Let's remove the macos platform from run-on-projects/by-test-platform for all Talos tests, allowing this platform to use the default value of ['mozilla-beta', 'trunk', 'try'].

Flags: needinfo?(mstange)
Flags: needinfo?(dave.hunt)
Pushed by fstrugariu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/7bede01766e0
Run macOS tests on integration branches r=perftest-reviewers,davehunt
Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
Assignee: nobody → fstrugariu
You need to log in before you can comment on or make changes to this bug.