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

Run clippy with nightly rust on CI #6347

Merged
merged 22 commits into from
Aug 16, 2018
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .travis.yml
Original file line number Diff line number Diff line change
Expand Up @@ -154,7 +154,7 @@ matrix:
env:
- SHARD="Self checks, lint, and JVM tests"
script:
- ./build-support/bin/ci.sh -fkmrjt "${SHARD}"
- ./build-support/bin/ci.sh -fkmrjst "${SHARD}"
Copy link
Member

Choose a reason for hiding this comment

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

The lint shard is not one of the shortest... while it's a bit odd, I'd wonder whether it would make more sense to do this on the rust tests shard.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, I was unsure between a new shard, the rust tests shard, and the lint shard...

The disadvantage of the test shard is that it conflates style issues with test issues, but I guess that's fine. I'm kind of tempted to just make it its own shard; there's very little set-up to do, now that we cache the rust toolchains...


- <<: *default_test_config
env:
Expand Down