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

build: Clean up "go vet" and "go lint" steps #2972

Closed
wants to merge 6 commits into from
Closed

build: Clean up "go vet" and "go lint" steps #2972

wants to merge 6 commits into from

Conversation

calmh
Copy link
Member

@calmh calmh commented Apr 13, 2016

Purpose

Vet was ugly, and was ignoring a composite literal warning for historical reasons. There is no reason to ignore it now. Also doing a bit better detection of the difference between an error because vet complains and an error because vet isn't installed.

// The actual return code is usually an uint16 (not sure why Go
// uses uint32). The high 8 bits of that are the exit code from
// the process, the lower 8 bits are signal info.
return int(code >> 8)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⁉️ I'd missed that that method exists!

@calmh
Copy link
Member Author

calmh commented Apr 15, 2016

I've fixed the exit status checking stupidity, thanks for catching it.

@AudriusButkevicius
Copy link
Member

@st-review merge

@st-review
Copy link

🕐 Build status is pending. I'll wait to see if this becomes successful and then merge!

@st-review
Copy link

👌 Merged as a4cd4cc. Thanks, @calmh!

@st-review st-review closed this Apr 15, 2016
st-review pushed a commit that referenced this pull request Apr 15, 2016
@calmh calmh deleted the vet branch April 15, 2016 11:14
@st-review st-review added the frozen-due-to-age Issues closed and untouched for a long time, together with being locked for discussion label Jun 16, 2017
@syncthing syncthing locked and limited conversation to collaborators Jun 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
frozen-due-to-age Issues closed and untouched for a long time, together with being locked for discussion
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants