Closed Bug 1604749 Opened 4 years ago Closed 4 years ago

daily cron job won't start

Categories

(Thunderbird :: Build Config, defect, P1)

defect

Tracking

(thunderbird_esr68 unaffected, thunderbird73 wontfix, thunderbird74 fixed)

RESOLVED FIXED
Thunderbird 74.0
Tracking Status
thunderbird_esr68 --- unaffected
thunderbird73 --- wontfix
thunderbird74 --- fixed

People

(Reporter: mkmelin, Assigned: rjl)

References

Details

Attachments

(8 files, 1 obsolete file)

Tom, Sorry to bother you with this. Any thoughts? I'll note that I did recently update our .taskcluster.yml file.

Flags: needinfo?(mozilla)

Notes:

My .taskcluster.yml change landed on Mon 2019-12-09. (bug 1504004)
Which broke actions in treeherder. Daily cron continued to work through Fri 12-12. IIRC that is due to bustage within Thunderbird. There was a Daily build on 2019-12-16.

It's noted in bug 1504004 comment 9 that actions are still busted. But Tom landed some ci-configuration changes at approx the same time which I believe fixed the actions because they work now. But that appears to have broken the Daily cron.

But oddly enough Periodic file updates cron worked just fine this morning.

More notes:

The issue appears to be specific to creating the "index" tasks.

index-task-build-linux64-shippable/opt
index-task-build-win64-shippable/opt
index-task-build-macosx64-shippable/opt
(possibly others)
Attached patch bug1604749.patch (obsolete) — Splinter Review
I'm basing this patch on suspicion that the "old" index routes are
being referenced when the cron decision task runs causing the failure,
and I should have kept them in Bug 1504004.
Attachment #9117809 - Flags: review?(geoff)
Attachment #9117809 - Flags: feedback?(mozilla)

Those routes weren't removed in bug 1504004. They never existed. :-/

Attachment #9117809 - Flags: review?(geoff)
Attachment #9117809 - Flags: feedback?(mozilla)

The index-build-* tasks get defined here: https://searchfox.org/mozilla-central/rev/c79fc6e32a5b561205a71fcfef9112d34b4037ae/taskcluster/taskgraph/morph.py#51

Always on a gecko-t/misc worker.

Looks like this removed access for comm repos to those workers (bug 1596177):
https://hg.mozilla.org/ci/ci-configuration/rev/f4f25ddf50561cc7c0e4ec117ea463fa2873f809

Index tasks pretty much only get generated for Thunderbird on release promotion and for Nightly builds. We will not be able to release beta or esr68 with this bug, so setting it as a blocker.

I see two potential fixes:

  • Create a comm-t/misc worker pool, grant access in ci-configuration, and then update morph.py to use it for Thunderbird builds. Then do the required uplift(s) to M-esr68 so releases work.
  • Grant access to gecko-t/misc to Thunderbird builds in ci-configuration/grants.yml

Patch coming for option 2 in the interest of expediency. If it's necessary I'll be happy to work on option 1.

Severity: normal → blocker
Flags: needinfo?(mozilla)
Priority: -- → P1

Since 2019-Dec-17 Thunderbird Nightly builds fail during the Cron Decision
task when creating the index-build tasks.
Those tasks run on gecko-t-misc workers. There is no equivalent comm-t-misc worker.

Attachment #9117809 - Attachment is obsolete: true
Pushed by mozilla@hocat.ca:
https://hg.mozilla.org/integration/autoland/rev/f6cf3ca2de50
Get misc worker-type from graph config; r=Callek
Looks like this will be needed after the next M-C merge,
Attachment #9118119 - Flags: review?(geoff)
Regressions: 1606387
Attachment #9118119 - Flags: review?(geoff) → review+
Pushed by mozilla@hocat.ca:
https://hg.mozilla.org/integration/autoland/rev/66a1c07a8f48
[taskgraph] Fix tests for index morph; r=Callek
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 73.0
Pushed by geoff@darktrojan.net:
https://hg.mozilla.org/comm-central/rev/489349930561
Add misc worker alias to config.yml. r=darktrojan
Regressions: 1606899
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

The original patch calculated the worker type, but didn't use it in the
generated task.

Is the plan to move Thunderbird to a 'comm-t/misc' worker for these?

(In reply to Tom Prince [:tomprince] from comment #17)

Created attachment 9124397 [details]
Bug 1604749: Get misc worker-type from graph config; r?Callek

The original patch calculated the worker type, but didn't use it in the
generated task.

Flags: needinfo?(mozilla)
Once D61780 lands in ci-configuration, we need to switch over to use comm-t
workers for indexing tasks.

This will need to be uplifted to comm-beta, and something will need to change
on comm-esr68 as well. This patch won't apply to c-esr68 though.
Attachment #9124640 - Flags: review?(geoff)

For esr68, "gecko-t" was hardcoded as the worker type:

https://searchfox.org/mozilla-esr68/source/taskcluster/taskgraph/morph.py#63

    task_def = {
        'provisionerId': 'gecko-t',
        'workerType': 'misc',
        'dependencies': [task.task_id, image_taskid],
        'created': {'relative-datestamp': '0 seconds'},

Are there uplift plans for the original work that allows setting the worker type in config.yml? We do have THUNDERBIRD_68_VERBRANCH on mozilla-esr68 that we build against with some Thunderbird-only changes already, so this could be one more of those if necessary.

Attachment #9124640 - Flags: review?(geoff) → review+

Pushed by thunderbird@calypsoblue.org:
https://hg.mozilla.org/comm-central/rev/c25b9b3f598a
Use comm-t/misc workers for index tasks. r=darktrojan

Status: REOPENED → RESOLVED
Closed: 4 years ago4 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: Thunderbird 73.0 → Thunderbird 74.0

(In reply to Magnus Melin [:mkmelin] from comment #23)

Dailies didn't run now, https://treeherder.mozilla.org/#/jobs?repo=comm-central&selectedJob=287910869

This isn't what broke it though.

Status: REOPENED → RESOLVED
Closed: 4 years ago4 years ago
Resolution: --- → FIXED
Flags: needinfo?(mozilla)

Rob, thunderbird_esr68 is still set as affected

Flags: needinfo?(rob)

It is and it isn't... nothing is actually broken on esr68 from our perspective. This bug was driven by a need to separate Thunderbird from Firefox a bit more in CI however, the code that we rely on in M-C to apply this patch is not on M-ESR68. I will check with them, but since we're rather late in ESR68's lifetime, I suspect that it won't happen and we can change that to a 'wontfix'.

Pushed by mozilla@hocat.ca:
https://hg.mozilla.org/integration/autoland/rev/d154bbd8a45b
Get misc worker-type from graph config; r=Callek

Tom indicated that we should be okay on esr68 as the necessary scopes will be applied in ci-configuration.

Flags: needinfo?(rob)

Now that we have landed https://phabricator.services.mozilla.com/D61643
on central, beta and esr78, the only active comm-* branch that doesn't
have the fix is comm-esr8. Restict the scope to that branch, and we can
let that scope live out the life of that branch.

Pushed by mozilla@hocat.ca:
https://hg.mozilla.org/ci/ci-configuration/rev/10c72b3b4ce8
Limit gecko-t/misc on comm branches to comm-esr68; r=Callek
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: