Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

When I run with `--pantsd` I get the dreaded `10:38:50.41 [DEBUG] connecting to pantsd on port 44973 (attempt 1/3)
Failed to launch child `/var/lib/buildkite-agent/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.0_py36/bin/pants`: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }` error.

Not sure if the two failures are related.

One is a failure to connect to the launched `pantsd` and one is the failure to find `python3.6`.

cicd-fail

Why do you assert "failure to connect"? That reads more like failure to run a binary.

Good point. I was using the debug line before as my guide (connecting to...)

```ts/setup/bootstrap-Linux-x86_64/2.0.0_py36/bin/pants
  File: /var/lib/buildkite-agent/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.0_py36/bin/pants
  Size: 306       	Blocks: 8          IO Block: 4096   regular file
Device: 10302h/66306d	Inode: 4614039     Links: 1
Access: (0775/-rwxrwxr-x)  Uid: (  999/buildkite-agent)   Gid: (  999/buildkite-agent)
Access: 2020-11-09 23:15:43.856779291 -0500
Modify: 2020-11-09 23:15:43.848783291 -0500
Change: 2020-11-09 23:15:43.848783291 -0500
 Birth: -```

root seemed to be able to run it but got `no BUILDROOT` type errors.

`/var/lib/buildkite-agent/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.0_py36/bin/pants` is not a binary.

```#!/var/lib/buildkite-agent/.cache/pants/setup/bootstrap-Linux-x86_64/pants.0KECIN/install/bin/python3.6
# -*- coding: utf-8 -*-
import re
import sys
from pants.bin.pants_loader import main
if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0])
    sys.exit(main())```

And so is that shebang binary executable?

I'm doing all these tests as the `buildkite-agent`.

I have not made any changes to apparmor at this point. But I did try to turn it off yesterday when I was troubleshooting and that did not help.

Dropping back a bit. It sounds like the binaries needed are on PATH. Is there an intent to use PYENV in ci / are pyenv interpreters installed on ci machines?

No. This is an ubuntu box and I have not installed pyenv.

Ok, so that config is noisy for ci but harmless.

Our automation installed python2.7 and python3.6-dev.

Can you import distutils in that python3.6?

Was thinking of <https://github.com/pantsbuild/pex/issues/1027|https://github.com/pantsbuild/pex/issues/1027> which presents differently.