deepspeech win-b tasks pending piling up
Categories
(Taskcluster :: Services, defect)
Tracking
(Not tracked)
People
(Reporter: gerard-majax, Assigned: pmoore)
Details
We have 20 pending task for windows instances: https://community-tc.services.mozilla.com/worker-manager
There is no meaningful error reported: https://community-tc.services.mozilla.com/worker-manager/proj-deepspeech%2Fwin-b/errors
Assignee | ||
Comment 1•5 years ago
|
||
It looks at first glance like instances aren't being spawned, rather than that they are being spawned but not taking jobs:
https://us-east-1.console.aws.amazon.com/ec2/home?region=us-east-1#Instances:tag:Name=proj-deepspeech/win-b;sort=tag:Name
https://us-west-1.console.aws.amazon.com/ec2/home?region=us-west-1#Instances:tag:Name=proj-deepspeech/win-b;sort=tag:Name
https://us-west-2.console.aws.amazon.com/ec2/home?region=us-west-2#Instances:tag:Name=proj-deepspeech/win-b;sort=tag:Name
Assignee | ||
Comment 2•5 years ago
|
||
My bad, it turns out I was looking in the wrong amazon account...
Comment 3•5 years ago
|
||
These are in a different AWS account than where Pete was looking. Instances are being spawned, and in fact there are 16 of them, but they are probably crashing out of generic-worker but not shutting down. I've given Pete access to the right AWS account (sorry!) and he's going to have a look-see.
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 4•5 years ago
|
||
The problem was malformed secrets. These were deleted, old workers were terminated, and things returned to normal.
Description
•