travis: only run affected tests on PR checks about go-cloud HOT 8 CLOSED

Can Go even identify this? I wasn't aware that it could.

from go-cloud.

I'm asserting that given you know the changed files from upstream, you can identify which packages those files are in, then use some invocation of go list to then obtain the reverse dependencies, then test just those packages. Again, hypothetically, we have all that information.

from go-cloud.

Discussed offline with @cflewis. The general solution would take some work, but the vast majority of the time right now is being eaten up by the Goose tests, which are pretty self-contained. We can start with just a script that only runs the Goose tests if a Goose file is modified.

from go-cloud.

Goose/Wire tests only run conditionally now, which cuts the build time in half. The overall issue is still there, but the worst of it is over.

from go-cloud.

Can we close this out? Getting the packages is going to be super dominant over pretty much anything else we can do unless we write really slow integration tests (which are a different issue probably solved by Travis sharding).

from go-cloud.

I'm leaning towards keeping it open: consider that any tools that use the vgo loading scheme would could download less dependencies than the entire project if only the affected tests are run.

from go-cloud.

Also, doc changes (.md files) shouldn't run the linter or the test suite.

from go-cloud.

Obsolete.

from go-cloud.