https://github.com/pantsbuild/pants/pull/11856 to debug, added log statements for what's going on

This is so bewildering to me, including why it's flaky and I can only get it to fail in CI and not my Ubuntu devbox

22:01:06.28 [INFO] input snapshot files: ('shellcheck-v0.7.1.linux.x86_64.tar.xz',)
185
22:01:06.28 [INFO] input snapshot dirs: ('__output',)
186
22:01:06.28 [INFO] argv: ('/usr/bin/tar', 'xf', 'shellcheck-v0.7.1.linux.x86_64.tar.xz', '-C', '__output')
22:01:06.51 [INFO] output files: ('shellcheck-v0.7.1/LICENSE.txt', 'shellcheck-v0.7.1/README.txt', 'shellcheck-v0.7.1/shellcheck')
197
22:01:06.51 [INFO] output dirs: ('shellcheck-v0.7.1',)

The output files should have

__output

in the prefix, and we tell the

Process

that

output_dirs=("__output",)

, so presumably Tar is behaving correctly and writing there Using GNU Tar 1.30, which is very modern and supports the

-C

flag

Gr this keeps flaking. I think in the meantime to figuring out, I should disable Shellcheck internally :/ (no need to revert implementation)

This continues to bewilder me. In general in CI, it seems to flake about 25% of the time. In this PR where I run

lint ::

30 times with no local cache, I can't get it to fail once. I still can't get it to fail on macOS and Linux https://github.com/pantsbuild/pants/pull/11856 I'm running out of ideas (and am not going to think about this until Monday). But any thoughts on figuring out why this would stop flaking in that PR? My idea is to revert some of the changes like

--no-pantsd

and see if one of them is causing it

Oh!! Might this be a remote cache bug?!

Well I be darned, I reproduce when using the remote cache