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

Pants

<@U36F42BLY> : are you using a JVM that doesn't support those JVM options? like 9?

can't remember whether 8 blows up for any of those.

I just bumped the version to 1.2.1 and removed the whole `compile.zinc` section. Still errors.

<@U36F42BLY> : is there a nailgun process running?

<@U098ZNTCN>: contents of stdout/err
```
[10:56:29]: cat .pants.d/ng/ZincCompile_compile_zinc/std*
java.io.EOFException
	at java.io.DataInputStream.readInt(DataInputStream.java:392)
	at com.martiansoftware.nailgun.NGSession.run(NGSession.java:182)
NGServer 0.9.1 started on 127.0.0.1, port 59891.
```

(4 of them, matching the number of cpu cores)

<@U36F42BLY> : there should only be one per tool

<@U36F42BLY> : in any case, `./pants ng-killall`, and confirm that they've all been killed

(or clean-all, which does the same thing)

you_re_right.txt

<@U36F42BLY|jack.cheng> uploaded a file: <https://pantsbuild.slack.com/files/jack.cheng/F49F12CSC/you_re_right.txt|you're right>

did ng-killall, and retried, but still errors

```
11:00:02 00:00     [ng-killall]INFO] killing nailgun server pid=22476
INFO] killing nailgun server pid=23157
INFO] killing nailgun server pid=23226
INFO] killing nailgun server pid=27400
```
and ps showed nothing afterwards

<@U36F42BLY> : try with `--no-compile-zinc-use-nailgun` ?

That seems to be working. No errors yet and things are compiling.

you definitely want to use nailgun... the goal there was just to try to get that error in the foreground.

<@U054MQUPL> : any ideas on this one? stale pid file?

you can just remove from abundance of caution