Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Travis CI failing to find goveralls on latest go version #207

Open
saheljalal opened this issue Oct 3, 2021 · 1 comment
Open

Travis CI failing to find goveralls on latest go version #207

saheljalal opened this issue Oct 3, 2021 · 1 comment

Comments

@saheljalal
Copy link

Travis CI is failing with the tip for go and passes with the same config using 1.13.x. It shows that it can't find the goveralls command.

The env:

go version devel go1.18-3bbc82371e Sat Oct 2 17:29:46 2021 +0000 linux/amd64
$ export GOPATH="/home/travis/gopath"
$ export PATH="/home/travis/gopath/bin:/home/travis/.gimme/versions/go/bin:/home/travis/bin:/home/travis/bin:/home/travis/.local/bin:/usr/local/lib/jvm/openjdk11/bin:/opt/pyenv/shims:/home/travis/.phpenv/shims:/home/travis/perl5/perlbrew/bin:/home/travis/.nvm/versions/node/v8.12.0/bin:/home/travis/.rvm/gems/ruby-2.5.3/bin:/home/travis/.rvm/gems/ruby-2.5.3@global/bin:/home/travis/.rvm/rubies/ruby-2.5.3/bin:/home/travis/gopath/bin:/home/travis/.gimme/versions/go1.11.1.linux.amd64/bin:/usr/local/maven-3.6.3/bin:/usr/local/cmake-3.12.4/bin:/usr/local/clang-7.0.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/home/travis/.rvm/bin:/home/travis/.phpenv/bin:/opt/pyenv/bin:/home/travis/.yarn/bin"
$ export GO111MODULE="on"
$ go version
go version devel go1.18-3bbc82371e Sat Oct 2 17:29:46 2021 +0000 linux/amd64
$ go get golang.org/x/tools/cmd/cover
$ go get github.com/mattn/goveralls

The error:

$ goveralls -coverprofile=coverage.out -service=travis-ci -repotoken $COVERALLS_TOKEN
No command 'goveralls' found, did you mean:
 Command 'coveralls' from package 'ruby-coveralls' (universe)
goveralls: command not found
The command "goveralls -coverprofile=coverage.out -service=travis-ci -repotoken $COVERALLS_TOKEN" exited with 127.
@brianV
Copy link

brianV commented Apr 21, 2022

I can confirm that this happens on CircleCI as well when running Go 1.18. This does not occur when I run it under Go 1.17.

nkinkade added a commit to m-lab/pusher that referenced this issue May 11, 2022
The travis build was failing with something like this:

mattn/goveralls#207

... and the Docker build was failing with this error:

Step 8/10 : COPY --from=build /go/bin/pusher /
COPY failed: stat go/bin/pusher: file does not exist
nkinkade added a commit to m-lab/pusher that referenced this issue May 12, 2022
* Removes old, empty directories

Pusher did not remove old directories. Every extant directory creates an
inotify watch in pusher. Over time and/or for experiments (e.g., wehe)
that create a large amount of directories, this can create a very large
number of useless watches, which eat up memory, and eventually may run
up against fs.inotify.max_user_watches, causing other containers on the
system to fail.

This commit also fixes an apparent variable name bug in which the value
for maxFileAge was put into a variable named minFileAge.

* Removes old, empty directories when walking dir

Previously, directories were not touched. On long-running containers
directories would begin to pile up causing a large amount of useless
pusher inotify directories watches.

* Uses Go v1.18 to build Docker image, and Alpine 3.15

* Updates Go modules

* Reverts prometheus/client_golang to v1.11.0

I was running into this with newer versions:

prometheus/prometheus#10574

* Updates Travis to use Go v1.18

* Reverts Go to v1.17 (from v1.18)

The travis build was failing with something like this:

mattn/goveralls#207

... and the Docker build was failing with this error:

Step 8/10 : COPY --from=build /go/bin/pusher /
COPY failed: stat go/bin/pusher: file does not exist

* Adds a clarifying comment about removing dirs

* Simplifies dir removal logic, removes branching
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants