Closed
Bug 1246004
Opened 10 years ago
Closed 8 years ago
interactive task doesn't terminate when all clients have disconnected!
Categories
(Taskcluster :: Workers, defect)
Taskcluster
Workers
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jonasfj, Assigned: wcosta)
Details
(Whiteboard: [docker-worker])
For some reason disconnecting the websocket doesn't kill the terminal...
This is a problem as the interactive tasks will run until maxRunTime.
| Reporter | ||
Comment 1•10 years ago
|
||
or maybe it does:
https://tools.taskcluster.net/task-inspector/#U2sfJVXVRKCyWXIa2lP2pA/
Or maybe the websocket server needs some option where it pings the client regularly to detect that the connection was lost...
I disconnected from the task above after 12 minutes, and it had 60 minutes maxRunTime.
Updated•9 years ago
|
Whiteboard: [docker-worker]
Updated•9 years ago
|
Component: Docker-Worker → Worker
| Assignee | ||
Comment 2•8 years ago
|
||
jonasfj, is this still valid?
Assignee: nobody → wcosta
Status: NEW → ASSIGNED
Flags: needinfo?(jopsen)
QA Contact: pmoore
| Reporter | ||
Comment 3•8 years ago
|
||
No idea, it could be fixed, who knows..
Basically, this is something you can test if you want.
I'm also okay with closing it and reopen if we discover it again, it's quite possible that this was fixed.
Flags: needinfo?(jopsen)
| Assignee | ||
Updated•8 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Updated•7 years ago
|
Component: Worker → Workers
You need to log in
before you can comment on or make changes to this bug.
Description
•