Raptor tests on Beta are running on both opt & pgo builds

RESOLVED FIXED in Firefox 68

Status

defect
P1
normal
RESOLVED FIXED
3 months ago
3 months ago

People

(Reporter: RyanVM, Assigned: rwood)

Tracking

unspecified
mozilla69
Points:
---

Firefox Tracking Flags

(firefox68 fixed, firefox69 fixed)

Details

Attachments

(1 attachment)

I noticed today that Raptor tests are running on both opt and PGO Android builds. Given that we have limited capacity for these tests, we probably want to get rid of the opt runs so just PGO remains.

Assignee: nobody → rwood
Status: NEW → ASSIGNED
Component: General → Raptor
Priority: -- → P1
Product: Release Engineering → Testing
QA Contact: catlee

Raptor android opt runs currently running on beta (and also running on pgo), that need to be disabled:

tp6m-c-1, 2, 3 4, 5, and 6
speedometer
tp6m-5, 6, and 8

This, alongside my change in bug #1553310 may explain the backlog of tasks on P2? Or are they in separate pools of devices?

./mach try fuzzy --full

Exception: Multiple matching values for test-platform u'android-hw-p2-8-0-arm7-api-16/opt' found while determining item run-on-projects in raptor-tp6m-2-geckoview-cold

hmm I don't see why

Ah maybe I need to update the first entry (android-hw-p2-8-0-arm7.*) to be .pgo.

    by-test-platform:
        android-hw-p2-8-0-arm7.*: ['try', 'mozilla-central']
        android-hw-.*-api-16/opt: ['try', 'trunk']
        android-hw-.*-aarch64/opt: ['try', 'trunk']

That fixed it. Updated phab, try push (although can't test on beta, just a 'sanity' check):

https://treeherder.mozilla.org/#/jobs?repo=try&revision=5641a2d0d595e26e7d487428429722a263127ca3

Pushed by rwood@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/440bee55379e
Raptor tests on Beta are running on both opt & pgo builds r=jmaher
Status: ASSIGNED → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
Whiteboard: [checkin-needed-beta]
Whiteboard: [checkin-needed-beta]
You need to log in before you can comment on or make changes to this bug.