Timeout when trying to close container

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
4 years ago
9 months ago

People

(Reporter: kgrandon, Unassigned)

Tracking

Details

(Reporter)

Description

4 years ago
It seems all tests pass, but sometimes we can't close the container. This seems to happen pretty frequently on GU10 - I haven't seen it on other runs yet, so I wonder if tests could be doing something bad?

*** UTM:SVC TimerManager:notify - notified @mozilla.org/b2g/webapps-update-timer;1
*** UTM:SVC TimerManager:notify - notified @mozilla.org/addons/integration;1
*** UTM:SVC TimerManager:notify - notified @mozilla.org/extensions/blocklist;1
*** UTM:SVC TimerManager:notify - notified timerID: user-agent-updates-timer
*** UTM:SVC TimerManager:registerTimer - id: user-agent-updates-timer
[taskcluster] Task timeout after 1800 seconds. Force killing container.
[taskcluster] Unsuccessful task run with exit code: -1 completed in 1914.042
seconds

https://taskcluster-artifacts.s3-us-west-2.amazonaws.com/H_4SRd7CR_mht1capFHx4w/4/public/logs/live_backing.log?AWSAccessKeyId=AKIAIZOQG4W6WG3PH3RQ&Expires=1414972955&Signature=WFrdY5TTwJQbbTRjypGFJM%2BvIMc%3D

Comment 1

3 years ago
Kevin, is this an issue any longer for you?
(Reporter)

Comment 2

3 years ago
Don't think I've seen it, probably safe to close. Thanks.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME

Updated

9 months ago
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.