Bots should manage $TMPDIR, $TMP, $TEMP to achieve better hermeticity |
||||||||||
Issue descriptionCurrently: * builds leak files into these directories * builds that crash or leak handles sometimes leak locks between multiple builds on the same machine. Since all builds currently share the same tempdir, this means that leaked lockfiles or simply having files opened on windows causes issues between builds * no clean way to 'clean' the tempdir; currently we use a big hammer that does a 'try to delete everything and hope for the best' pass on temp The solution here is to have the builders set unique values for the various temp environment variables before running the task. Additionally, when the task starts, they'll attempt to delete any existing temporary directories that were leftovers.
,
Mar 8 2017
,
Mar 8 2017
Also blocked on b/36039166
,
Mar 8 2017
,
Mar 8 2017
It looks like there's some other interesting stuff going on with client.art too (besides the path length stuff): https://luci-milo.appspot.com/buildbot/client.art/hammerhead-concurrent-collector/2705 It looks like that master runs multiple builds on the same slaves simultaneously (!!).
,
Mar 8 2017
,
Mar 8 2017
Looks like some cumulative knowledge from the various blockers: * On windows, place temp dir in C:\ to avoid cross-volume issues * On linux, drop pid files/hold flocks in temp dirs to avoid issues like the ones seen on the art builder (where multiple slaves run on the same host at the same time).
,
Apr 27 2017
,
May 4 2017
,
Jun 21 2017
,
Jul 25 2017
,
Aug 14 2017
,
Jun 16 2018
pri-3 because luci |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by iannu...@google.com
, Mar 8 2017