You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Which problem is this PR solving?
- Resolves#5043
## Description of the changes
- `go-junit-report` was getting installed successfully into the default
`$GOPATH` (`$HOME/go/bin`) but the GOPATH wasn't in the `$PATH`
environment variable, which is what caused the `go-junit-report: command
not found` error.
- It worked for the normal (non-go-tip) unit tests because the `$GOPATH`
was already set and inserted into `$PATH`.
- This explicitly sets the `$GOPATH` and inserts it into `$PATH` prior
to installing test tools.
## How was this change tested?
- Tested in [my own
fork](https://github.com/albertteoh/jaeger/actions/runs/7332463204/job/19966641893)
with some debug logging in the Makefile.
## Checklist
- [x] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [x] I have signed all commits
---------
Signed-off-by: Albert Teoh <albert@packsmith.io>
Co-authored-by: Albert Teoh <albert@packsmith.io>
https://github.com/jaegertracing/jaeger/actions/runs/7330978812/job/19962951731
The tool is being installed, although strangely it lists both v1 and v2
but then it fails saying
command not found
cc @albertteoh
The text was updated successfully, but these errors were encountered: