Closed
Bug 1622052
Opened 5 years ago
Closed 5 years ago
worker-runner protocol negotiation issues
Categories
(Taskcluster :: Workers, defect)
Taskcluster
Workers
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
References
(Blocks 1 open bug)
Details
- protocol.Capable only looks at the local capabilities, not those of the remote end. This is causing failures in g-w unit tests now (but will not affect performance for users)
- it's still possible to add capabilities after the protocol has started -- it shoudln't be.
- the JS implementation in docker-worker is not quite up to the same standards
Assignee | ||
Comment 1•5 years ago
|
||
https://github.com/taskcluster/taskcluster/pull/2501
That covers 1 and 2.
Assignee | ||
Comment 2•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•