sound: extend CI checks #14
Conversation
Mostly to tickle a new build on Travis-CI.
|
I added ci_checks.sh to meta |
|
LGTM |
|
sorry, didn't mean to close |
This reverts commit 5085123.
I couldn't get code coverage reporting to work with the token you sent, so had to update and trouble shoot the ci_checks script. And I don't have access to zc/meta as far as I know. |
This reverts commit 1442230.
|
Github tells me you have admin access on all zc repos. |
|
Oh well, we can live without code coverage reporting for now. I tried to trouble shoot why the if [ "${COVERALLS_TOKEN}" ]; then
echo "### go tool cover"
go test -covermode=count -coverprofile=coverage.out ./...
go tool cover -func coverage.out
# To submit the test coverage result to coveralls.io use goveralls
# (https://github.com/mattn/goveralls)
goveralls -coverprofile coverage.out -service travis-ci -repotoken ${COVERALLS_TOKEN}
fi |
Oh, that's more than I know. I thought I was only part of |
|
Feel free to merge this and then the got to go. Cheers, |
|
Since we've got so many CI build issues, maybe I'll clean up the various more cosmetic issues from these new CI checks in the repo first... |
|
Looking more closely, it seems the linter is checking whether error return values are checked? I don't like that; for example, when using sndbuf there are no io errors but it has them to fit the interface. Is there some way to refine the linter checks or the files on which they operate? Don't want to lose a badge over something like that :( |
|
any ideas on how to make travis recognise stdatomic.h via cgo? |
|
It should work with newer versions of GCC, as suggested in cmus/cmus#604 If there is something specific to Cgo that prevents it from working, I don't know. |
Add GolangCI meta linter among others.
Code coverage token will be added in a follow-up PR.