aboutsummaryrefslogtreecommitdiffhomepage
path: root/Rakefile
diff options
context:
space:
mode:
authorGravatar Jan Tattermusch <jtattermusch@google.com>2018-02-05 15:35:31 +0100
committerGravatar Jan Tattermusch <jtattermusch@google.com>2018-02-05 17:44:15 +0100
commitfb1ad359841ce016589a68fca6685fcba3125c5d (patch)
tree17f6d3daa3482438910711ac51e5e3c6925d1d73 /Rakefile
parent73a50abd1d675acba4bdbde3af8ca0077654de79 (diff)
Using python's xdg-caching can cause flakes
Currently when running python test on linux, we are mounting /tmp/xdg-cache-home to the docker container that runs the tests in the attempt to prevent unnecessary downloads of pip packages (with the theory that more downloads leads to increased flakiness) - the idea is that while there is a new docker container for each test suite, the xdg cache remains per-VM. This approach no longer seems to be useful: * It turns out that XDG cache doesn't work reliably when multiple docker containers are using it concurrently (the concurrent run can see corrupt files). We are using concurrent docker containers in our multilang test suite to speed up the execution and we are currently getting flakes seeing flakes caused by this. * support for caching makes our docker_run scripts more complicated and we really don't want that. * since we migrated to kokoro, the caching is limited anyway - as each run gets a fresh VM, we need to download packages anyway for every build (and that actually seems to causing way less flakiness the problem with concurrent XDG caching).
Diffstat (limited to 'Rakefile')
0 files changed, 0 insertions, 0 deletions