Perform additional checks in Travis CI. about go-cmp HOT 5 CLOSED

For reference, I've sent a similar change to .travis.yml to github.com/gorilla/mux in 2015 and it was accepted there, see gorilla/mux#134.

from go-cmp.

Suggested script LGTM, but avoid the go get step for now. It is intended for this package to have no dependencies other than the standard library. We can add that in if this ever changes.

Unrelated to this repo, it would be really cool if there was a way to setup travis to send failures on master to some dashboard that the core Go developers could look at it. This would be a great form of distributed regression testing. As it stand, we rely heavily on users manually reporting issues.

from go-cmp.

Suggested script LGTM, but avoid the go get step for now. It is intended for this package to have no dependencies other than the standard library. We can add that in if this ever changes.

SGTM, I'll do that.

Unrelated to this repo, it would be really cool if there was a way to setup travis to send failures on master to some dashboard that the core Go developers could look at it. This would be a great form of distributed regression testing. As it stand, we rely heavily on users manually reporting issues.

This is an interesting idea. I have seen it suggested in the past, and we discussed what it would take to make that possible. Unfortunately, after spending 15~ mins I couldn't find where that discussion took place. :( IIRC, the general conclusion was that there are many false positives, and as a result, it ends up being quite optimal to rely on people manually peeking at the tip failures of their own projects from time to time, investigating the root cause, and reporting a detailed and helpful bug report upstream to Go only when the problem is indeed in the toolchain, rather than elsewhere.

from go-cmp.

Ohhh, I found it! @dsnet, you were the person who made the suggestion. 😆

See golang/lint#279 (comment).

from go-cmp.

Ha... I often forget the very words I say :)

from go-cmp.