Interactive shell fails to execute `bin/checkout-gecko-and-run` because `/home/worker/hg-shared` does not exist

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
2 years ago
4 months ago

People

(Reporter: whimboo, Unassigned)

Tracking

Details

(Reporter)

Description

2 years ago
I tried to run TC tasks manually by requesting a loaner for the following Mozharness unit test job:

https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=8322ffecd9d90d31ff451cd9763fe2cfa5ae09b4&selectedJob=1414486

When I enter the root shell and execute the following command, it spits out a failure and exits right away:

> $ bin/checkout-gecko-and-run /home/worker/workspace/gecko
> ++ id -u
> + '[' 0 = 0 ']'
> + mkdir -p /home/worker/workspace
> + chown worker:worker /home/worker/hg-shared /home/worker/workspace
> chown: cannot access '/home/worker/hg-shared': No such file or directory

I talked with Pete on IRC and maybe that is due to security or safety reasons, but even if we cannot mount we should create an empty `hg-shared` folder so that `checkout-gecko-and-run` does not break.
so similar to how we create /home/worker/workspace we should create /home/worker/hg-shared because on  Try this directory will not exist because the cache is stripped from the payload definition when creating the interactive task.
Component: Docker-Worker → Task Configuration
run-task should arguably react better when the cache directory isn't present.

Although, I want it to fail by default if the hg-shared cache isn't present because not using that cache will make things much, much slower. How about an environment variable "DO_NOT_REQUIRE_HG_SHARED" or similar?
Greg, is this something you can hack on, or possibly a mentored/good-first bug?
Component: Task Configuration → Docker Images
Flags: needinfo?(gps)
Unless this is a high-ish priority, I don't have the cycles to hack on this :/
Flags: needinfo?(gps)
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX

Updated

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