packet.net workers seem to not have TASKCLUSTER_ROOT_URL in their environment
Categories
(Taskcluster :: Workers, defect)
Tracking
(Not tracked)
People
(Reporter: kats, Unassigned)
References
Details
This is trying to run fetch-content on a packet.net worker and it fails because it expects os.environ to have TASKCLUSTER_ROOT_URL but it doesn't.
Reporter | ||
Updated•6 years ago
|
Comment 1•6 years ago
|
||
The reason is that packet.net runs an old version of docker-worker. Theoretically, it is a simple fix, but I won't have time anytime soon because of GCP.
Comment 2•6 years ago
|
||
I am going to close this bug because this is fixed in the image based instances.
Reporter | ||
Comment 3•6 years ago
|
||
Can you explain what you mean by image based instances? What I really want to know is if I can remove these env vars.
Comment 4•6 years ago
|
||
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #3)
Can you explain what you mean by image based instances? What I really want
to know is if I can remove [these env
vars](https://searchfox.org/mozilla-central/rev/
7556a400affa9eb99e522d2d17c40689fa23a729/taskcluster/ci/webrender/kind.
yml#309-310,349-350).
We currently provision the instance from the ground up when it launches, we are working in creating a custom packet.net image (similarly to an AMI) to speed up instance startup. For now, it is not production ready yet.
Reporter | ||
Comment 5•6 years ago
|
||
Can we leave this bug open (retitled appropriately) such that closing it will allow removal of the env vars? Alternatively, if there is no plan to allow that removal, then I can just remove the reference to this bug in the yml file.
Comment 6•6 years ago
|
||
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #5)
Can we leave this bug open (retitled appropriately) such that closing it
will allow removal of the env vars? Alternatively, if there is no plan to
allow that removal, then I can just remove the reference to this bug in the
yml file.
Yes, sure, feel free to retitle the bug.
Updated•5 years ago
|
Comment 7•5 years ago
|
||
What is the state here? We have two references in tree to this bug.
https://searchfox.org/mozilla-central/source/taskcluster/ci/webrender/kind.yml#328
https://searchfox.org/mozilla-central/source/taskcluster/ci/webrender/kind.yml#368
[sending n-i to coop since wander and kats have n-i's blocked]
Comment 8•5 years ago
|
||
(In reply to Justin Wood (:Callek) from comment #7)
What is the state here? We have two references in tree to this bug.
https://searchfox.org/mozilla-central/source/taskcluster/ci/webrender/kind.yml#328
https://searchfox.org/mozilla-central/source/taskcluster/ci/webrender/kind.yml#368[sending n-i to coop since wander and kats have n-i's blocked]
We should be cutting over to AWS for these tests very early in January (bug 1578460). It's the most important thing on Wander's plate when he returns.
Description
•