Swarming should make $HOME a per-task temporary folder |
||||
Issue descriptionIssue: some tools (like vpython) pick a default cache directory of $HOME/<something>. Currently swarming bots don't isolate this per-task, which means that we could have some 'hidden state' which affects the reproducibility of the task. If tasks SHOULD share state, we have named caches for that. Otherwise this hidden coupling could definitely impact correctness/speed/debuggability of tasks (e.g. if vpython cache was corrupted it could spill into many tasks but go hidden because it's not a shared cache). My proposal would be to have the swarming bot pick a task subdirectory (maybe .../h) and assign that value to $HOME when running the task. This directory would get cleaned like the rest of the task dirs and prevent accidental coupling.
,
Feb 12 2018
+vadim too. One thing I think this may impact are puppet-deployed config files (like .gitconfig)... I don't /think/ credentials are deployed here still, but we may still be relying on e.g. gitcookies. A way to mitigate this would be to have bots.cfg explicitly list the file(s) to copy from real HOME to the per-task home. I think in general we are trying to move away from deployed-in-$HOME stuff, but maybe there's a reason we should keep this unrestricted?
,
Feb 21 2018
Blocking on issue 808836, as I think this fits with the story of defining a containment story.
,
Dec 19
|
||||
►
Sign in to add a comment |
||||
Comment 1 by iannucci@chromium.org
, Feb 12 2018