Closed Bug 1230511 Opened 9 years ago Closed 7 years ago

Various problems running "Run locally" instructions

Categories

(Taskcluster :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: glandium, Unassigned)

References

Details

I know this used to work, because I've used it in the past, but today, it just didn't work.

I took the instructions from https://tools.taskcluster.net/task-inspector/#cDDEvmKZRPOBwae8ubLuWA/

This is what I got first:
(...)
+ for cache in /home/worker/.tc-vcs /home/worker/workspace /home/worker/tooltool-cache
+ chown -R worker:worker /home/worker/.tc-vcs
chown: cannot access `/home/worker/.tc-vcs': No such file or directory

So I ran /bin/bash without bin/build.sh, then created the missing directories: /home/worker/.tc-vcs and /home/worker/tooltool-cache

Then started bin/build.sh again.

Which ended up failing because tooltool tries to download from http://relengapi/tooltool, which doesn't resolve.

After running tooltool manually with an url that works, retrying finally starts the build, but fails quickly with:

IOError: [Errno 28] No space left on device

because:

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/docker-202:1-399397-2b34f3fa740461ac470d764c170248f52ba5930370c1be8a9475ca1e3814f934
                      9.8G  9.3G  4.0K 100% /
The latter is due to the lack of aufs on my system.
(In reply to Mike Hommey [:glandium] from comment #0)
> Which ended up failing because tooltool tries to download from
> http://relengapi/tooltool, which doesn't resolve.

Random observation: without a --url, tooltool uses the right server. That could be leveraged.
In fact, tooltool could read a config file from $HOME. The config file could change the default url tooltool uses. The TC environment could have such a config pointing to http://relengapi/tooltool. Then on a local machine, where $HOME is not mounted from the host and won't contain that config, the right url would be used automatically.
There have been many known limitations of the "run locally" section and it was removed.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.