Closed Bug 1535057 Opened 2 years ago Closed 2 years ago

Chromium cron update does not trigger new chromium builds

Categories

(Testing :: Raptor, defect)

Version 3
defect
Not set
normal

Tracking

(firefox67 fixed)

RESOLVED FIXED
mozilla67
Tracking Status
firefox67 --- fixed

People

(Reporter: sparky, Assigned: tomprince)

References

Details

Attachments

(1 file)

Bug 1476372 made it possible to update the chromium build in use to the latest one on a daily basis but the cron task is not scheduling them. See here for an example: https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&tier=1%2C2%2C3&searchStr=chromium&revision=4d15e90af575a68815975bac8c2b602f78d76ee8

:tomprince, in the review for bug 1476372 you mentioned that you can make a follow-up patch to get this to work, would you be able to do this in this bug?

Flags: needinfo?(mozilla)

Apparently I had already landed the support code in Bug 1514087, I'll submit a patch to enable it for this as well.

Flags: needinfo?(mozilla)

We have a cron job to update the chromium, but the tasks were getting optimized
away. Force the target tasks for the cron job to always run.

Pushed by mozilla@hocat.ca:
https://hg.mozilla.org/integration/autoland/rev/57387d4ed085
Always re-fetch chromium in cron; r=aki

Perfect, thanks :tomprince!

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
Assignee: nobody → mozilla
You need to log in before you can comment on or make changes to this bug.