-
Notifications
You must be signed in to change notification settings - Fork 67
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
github: Run go test in CI #201
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason you dont use go test go-dqlite/...?
@markylaing I would appreciate your thoughts on this one given youve done a lot of our github ci stuff lately. Thanks |
I'm not super familiar with the Go command-line syntax, so I just copied what Launchpad was doing. I'll simplify it, one sec... |
Thanks you could take a look at what we do in the lxd github repo, as that way we won't need to remember to add each sub package to the list. Probably worth updating launchpad too otherwise things may be missed there also. Thanks |
5c801de
to
c67cb35
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why vet off btw?
Why vet off btw?
That's also as in Launchpad -- I wanted to keep the two in sync, but I can
remove `-vet=off` in both places if you approve (and if you can point me to
where the definitions for the go-dqlite Launchpad build jobs live -- I
haven't been able to find them).
…On Wed, Sep 7, 2022 at 4:14 PM Tom Parrott ***@***.***> wrote:
***@***.**** commented on this pull request.
Why vet off btw?
—
Reply to this email directly, view it on GitHub
<#201 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMYX2CRRGWZ52KO3LSTPQUTV5DZUBANCNFSM6AAAAAAQHCIV4U>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Does go test pass with vet off removed? If so I see no reason to leave it disabled. As for launchpad I'm not sure but agree they should be in sync. @stgraber can you point us to where the launchpad build scripts are? Thanks |
Signed-off-by: Cole Miller <cole.miller@canonical.com>
Yes! Updated this PR. As for Launchpad, as far as I can tell, the arguments passed to |
The following line in the .github actions file takes care of it.
|
I had never heard of overalls before! Overall the test/lint actions in this repo look fine. We could use golangci-lint to add a few more linters like in LXD (see the static analysis target in the Makefile and the golangci-lint configuration file). |
Thanks @MathieuBordere, looks like we do get test failure reports from overalls, so I'll revert this. |
We already run
go test
on Launchpad, but not for pull requests. Not sure whether there's a reason for that, so I'm opening this PR to facilitate discussion.Signed-off-by: Cole Miller cole.miller@canonical.com