1374213 - ESR52 tasks currently require taskcluster-worker OS X workers, and we don't have any

Status: RESOLVED FIXED

(Taskcluster :: Services, defect)

Description

[Pete Moore [:pmoore][:pete]]

Context: http://logs.glob.uno/?c=taskcluster#c200665

07:56	KWierso|afk	taskcluster jobs on esr52 seem to be unhappy: treeherder.mozilla.org/#/jobs?repo…=10.%20tc&group_state=expanded
07:56	KWierso|afk	failing like queue.taskcluster.net/v1/task/N7N0…facts/public/logs/live_backing.log
07:56	KWierso|afk	do we need to uplift something to esr52 or un-move things from taskcluster on that tree?
07:56	KWierso|afk	back to buildbot/bbb?
08:11	* pmoore looks
08:16	pmoore	looks like e.g. task tools.taskcluster.net/task-inspector/#N7N0H-xaRX-1zHvwqRS4Ig never got claimed - let me check the provisionerId / workerType is correct ....
08:20	pmoore	wcosta: do you know what tc-worker-provisioner is? the only reference i can find is in bugzilla.mozilla.org/show_bug.cgi?id=1274980#c107
08:20	firebot	Bug 1274980 — FIXED, wcosta%mozilla.com — Configure test tasks for Mac OSX builds
08:24	pmoore	looks like it is coming from mozilla-esr52/annotate/796616713ef…ests/make_task_description.py#l393
08:25	pmoore	KWierso|afk: i suspect this needs renaming - indeed it might be an uplift, i think the provisioner was renamed on other trees
08:26	pmoore	i'll see if i can find what needs uplifting
08:26	KWierso|afk	pmoore: okay. 1:30am is my cutoff time for looking at things. will follow up in the morning :)
08:27	pmoore	KWierso|afk: sure no worries, i'll work with Tomcat|sheriffduty on this one. have a good night, and thanks for the heads up!
08:32	pmoore	hmmmm, this looks like a taskcluster-worker task, our pool is entirely generic-worker these days :/
08:33	pmoore	i guess the options are keeping a very small taskcluster-worker pool for these ESR jobs, or patching ESR to use generic-worker
08:33	pmoore	i'll create a bug

Comment 1

[Pete Moore [:pmoore][:pete]]

Full link from chat above is: https://hg.mozilla.org/releases/mozilla-esr52/annotate/796616713ef2887f42c361329602bbd04cbbf773/taskcluster/taskgraph/transforms/tests/make_task_description.py#l393

Comment 2

[Greg Arndt [:garndt]]

No jobs were migrated on the esr52 branch and these failures were present before the migration that started on June 13th.  It looks like esr52 maybe was created at a time where things were in flux and never received our newest automation scheduling code after that.  Those jobs indeed use a worker type that do not exist and the jobs will fail with deadline-exceeded.

Perhaps a patch specific to esr52 coudl be created that just disabled these from even trying to run?

Comment 3

[Wander Lairson Costa]

Attachment: esr52 tests should never be scheduled by tc. r=pmoore

Comment 4

[Wander Lairson Costa]

Comment on attachment 8879130 [details] [diff] [review]
esr52 tests should never be scheduled by tc. r=pmoore

Surprisingly how this bug was hidden all this time, since we shutdown taskcluster-worker machines a long time ago ¯\_(ツ)_/¯

Comment 5

[Wander Lairson Costa]

Uplifting this to esr52 should fix the issue.

Comment 6

[Pete Moore [:pmoore][:pete]]

Comment on attachment 8879130 [details] [diff] [review]
esr52 tests should never be scheduled by tc. r=pmoore

Review of attachment 8879130 [details] [diff] [review]:
-----------------------------------------------------------------

lgtm, thanks Wander!

Comment 7

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

This should be able to be uplifted a=test-only.

Comment 8

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/releases/mozilla-esr52/rev/d1f81cbeaae3