Closed alexec closed 3 years ago
Please clearify whether the output you showed came from go run
or go test
The output seems to suggest go run
and the last line before exit status is executeing your code.
What happens when you try go build
followed by executeing your program manually?
go build ./...
is successful. Both go test ./controllers
and go run .
fail, the output is as you said, from go run
.
I believe there is something in the controllers
package causing the problem, but I can't identify what. It makes me wonder if it is a Golang bug.
I realize I omitted the URL to the build that is failing:
https://github.com/argoproj-labs/argo-dataflow/actions/workflows/go.yml
go build ./... is successful. Both go test ./controllers and go run . fail, the output is as you said, from go run.
I meant doing a
go build .
./myprogram
You might get a more useful exit satus code that way.
Run ./bin/manager
./bin/manager
shell: /usr/bin/bash -e {0}
env:
GOROOT: /opt/hostedtoolcache/go/1.16.3/x64
Error: Process completed with exit code 1.
I also omitted to mention - this only fails on Github Actions - not on Linux or Darwin.
Can you do a EDIT: just saw you did one a while ago
Also have you confirmed that your error logging is working with github actions?
We need to rule out your program doing a go test -v ./...
it might help show which test is failing.os.Exit(1)
but the log wasn't captured for some reason.
If nothing seems to make sense, you can try running rr
on github actions to capture a trace file which you can then inspect with the dlv debugger locally.
https://github.com/rr-debugger/rr
https://github.com/go-delve/delve/blob/master/Documentation/usage/dlv_replay.md
Ok. I'm pretty sure I've tracked this to a call to ctrl.GetConfigOrDie()
in init()
. I'll close and re-open if I'm wrong.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
I should be able to run tests fine. Instead I get
exit code 1
and no other diagnostics.What did you see instead?