使用Java的Runtime.getRuntime（）。exec（）运行时，从源代码构建Go失败测试

Question

This question is related to a previous question, here: Java Runtime.getRuntime().exec() appears to be overwriting $PATH

I am trying to build Go from source from inside a Java program. I can build it properly using Terminal, but Java's Runtime.getRuntime().exec() gets interesting results. I tried using ProcessBuilder, but could not get it to properly make Go. Using my current setup with exec(), it makes properly, but then fails two tests. Code snippet:

String[] envp = new String[4];
envp[0] = "CC=/usr/bin/clang";
envp[1] = "GOROOT_BOOTSTRAP=/usr/local/go";
envp[2] = "CGO_ENABLED=0";
envp[3] = "PATH=" + System.getenv().get("PATH");
Runtime.getRuntime().exec("./all.bash", envp, "$HOME/Desktop/go/src");

It runs properly and compiles properly, but when it gets to running the test suite, I get two errors:

--- FAIL: TestCurrent (0.00s)
user_test.go:24: Current: user: Current not implemented on darwin/amd64 (got &user.User{Uid:"502", Gid:"20", Username:"", Name:"", HomeDir:""})
FAIL
FAIL    os/user 0.009s

and a much longer one that I won't paste here due to absurd length, but it comes down to:

panic: test timed out after 3m0s
...
FAIL    runtime 180.056s

I haven't any idea why the former is failing, but for the runtime when I build from the Terminal, it says:

ok      runtime 19.096s

So something is causing that to take absurd amounts of time. I did some googling, and heard that it might be fixed if I use ARM=5 as an environment variable, but that didn't change anything. Does anyone have any idea why these tests are failing when I build from Java as opposed to the Terminal?

Answer 1

Looking at the source code for the os/user package, it looks like the native user handling depends on having cgo enabled. If cgo=0 (your case), it will fall back to the USER and HOME environment variables.

source code in question

Try putting USER=whatever in your exec environment.

I'm afraid I'd need more information to diagnose the runtime issue.