Closed Bug 1838032 Opened 1 year ago Closed 2 months ago

./mach try perf doesn't seem to always trigger builds for the base build


(Testing :: Performance, defect, P2)



(Not tracked)



(Reporter: jesup, Unassigned)


(Depends on 1 open bug, Blocks 2 open bugs)


(Whiteboard: [fxp])

I frequently when doing a series of ./mach try perf runs have to go and manually trigger/retrigger tests on the base build (perhaps because I've changed which tests I'm triggering?)

:jesup, can you try rebasing your code and see if it still happens? I thought I had resolved this issue here, but maybe not: bug 1831603

We cache the base commit for 2 weeks, and before that patch landed it wasn't considering the tasks you selected but now it does. Note that it still won't handle retriggers that you request on it, but you can do that through the compare view (there's a column for it on the right-hand side).

Flags: needinfo?(rjesup)
Severity: -- → S3
Priority: -- → P2
Whiteboard: [fxp]

I'll see if I can repro this again

Flags: needinfo?(rjesup)

:jesup, can you provide the full log of one of these mach try perf runs? I'm wondering if it produced a compare view link, and what base revision it selected.

Flags: needinfo?(gmierz2) → needinfo?(rjesup)
Depends on: 1845789

It happened to me too, but only when I change the after commit and I don't rebase (basically, it won't push again an identical push with the previous one).

:jesup, is this bug still an issue for you? If so, could you provide some logs the next time you hit it (see comment #4).

Flags: needinfo?(rjesup)
Flags: needinfo?(rjesup)

If this happens again, I'll re-report with more info

Closed: 2 months ago
Flags: needinfo?(rjesup)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.