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

Update Clippy #58807

Merged
merged 1 commit into from
Mar 4, 2019
Merged

Update Clippy #58807

merged 1 commit into from
Mar 4, 2019

Conversation

Xanewok
Copy link
Member

@Xanewok Xanewok commented Feb 28, 2019

Should fix the fallout caused by #58321 (still testing it locally).

r? @oli-obk

@rust-highfive
Copy link
Collaborator

⚠️ Warning ⚠️

  • These commits modify submodules.

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 28, 2019
@Xanewok
Copy link
Member Author

Xanewok commented Feb 28, 2019

cc #58765

@Xanewok
Copy link
Member Author

Xanewok commented Feb 28, 2019

#58754 also contains the relevant clippy update when/if that lands

@ljedrz
Copy link
Contributor

ljedrz commented Feb 28, 2019

@Xanewok #58754 has a slightly bumped priority, so it should land soon (it's currently 5th in the queue).

Oh and it will land; there's way too much further work depending on it for me to forget about it ^^.

@kennytm
Copy link
Member

kennytm commented Mar 2, 2019

#58754 has been merged.

@ljedrz
Copy link
Contributor

ljedrz commented Mar 2, 2019

@kennytm unfortunately without the clippy update; now #58836 has one, but it might need a different clippy update due to tidy not allowing the custom compiletest-rs branch.

TL;DR: I think this PR should be merged (as long as it doesn't suffer from the other breakage)

@Xanewok
Copy link
Member Author

Xanewok commented Mar 2, 2019

If the API is meant to be 1-1 compatible, maybe it'd make sense to patch the compiletest-rs to point to https://github.com/rust-lang/rust/tree/master/src/tools/compiletest (just like we do with Rustfmt and clippy in-tree)? I think this should unblock the releases until Manishearth/compiletest-rs#160 is merged and a new version is released.

@mati865
Copy link
Contributor

mati865 commented Mar 2, 2019

@Xanewok I think that's good idea, tools upgrades would no longer be blocked when some changes break compiletest-rs.

@rust-highfive
Copy link
Collaborator

The job x86_64-gnu-llvm-6.0 of your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.

Click to expand the log.
travis_time:end:351d602c:start=1551620963756334604,finish=1551620964701404391,duration=945069787
$ git checkout -qf FETCH_HEAD
travis_fold:end:git.checkout

Encrypted environment variables have been removed for security reasons.
See https://docs.travis-ci.com/user/pull-requests/#pull-requests-and-security-restrictions
$ export SCCACHE_BUCKET=rust-lang-ci-sccache2
$ export SCCACHE_REGION=us-west-1
Setting environment variables from .travis.yml
$ export IMAGE=x86_64-gnu-llvm-6.0
---
[00:01:57] 
######################################################################## 100.0%
[00:01:57] extracting /checkout/obj/build/cache/2019-02-27/cargo-beta-x86_64-unknown-linux-gnu.tar.gz
[00:01:57]     Updating crates.io index
[00:02:10]     Updating git repository `https://github.com/mati865/compiletest-rs.git`
[00:02:10] error: the lock file /checkout/Cargo.lock needs to be updated but --locked was passed to prevent this
[00:02:10] Build completed unsuccessfully in 0:00:25
[00:02:10] Makefile:70: recipe for target 'prepare' failed
[00:02:10] make: *** [prepare] Error 1
[00:02:11] Command failed. Attempt 2/5:
[00:02:11] Command failed. Attempt 2/5:
[00:02:11]     Updating git repository `https://github.com/mati865/compiletest-rs.git`
[00:02:12] error: the lock file /checkout/Cargo.lock needs to be updated but --locked was passed to prevent this
[00:02:12] Build completed unsuccessfully in 0:00:00
[00:02:12] Makefile:70: recipe for target 'prepare' failed
[00:02:12] make: *** [prepare] Error 1
[00:02:14] Command failed. Attempt 3/5:
[00:02:14] Command failed. Attempt 3/5:
[00:02:14]     Updating git repository `https://github.com/mati865/compiletest-rs.git`
[00:02:14] error: the lock file /checkout/Cargo.lock needs to be updated but --locked was passed to prevent this
[00:02:14] Build completed unsuccessfully in 0:00:00
[00:02:14] Makefile:70: recipe for target 'prepare' failed
[00:02:14] make: *** [prepare] Error 1
[00:02:17] Command failed. Attempt 4/5:
[00:02:17] Command failed. Attempt 4/5:
[00:02:17]     Updating git repository `https://github.com/mati865/compiletest-rs.git`
[00:02:18] error: the lock file /checkout/Cargo.lock needs to be updated but --locked was passed to prevent this
[00:02:18] Build completed unsuccessfully in 0:00:00
[00:02:18] Makefile:70: recipe for target 'prepare' failed
[00:02:18] make: *** [prepare] Error 1
[00:02:22] Command failed. Attempt 5/5:
[00:02:22] Command failed. Attempt 5/5:
[00:02:22]     Updating git repository `https://github.com/mati865/compiletest-rs.git`
[00:02:22] error: the lock file /checkout/Cargo.lock needs to be updated but --locked was passed to prevent this
[00:02:22] Build completed unsuccessfully in 0:00:00
[00:02:22] Makefile:70: recipe for target 'prepare' failed
[00:02:22] make: *** [prepare] Error 1
[00:02:22] The command has failed after 5 attempts.
---
travis_time:end:0ece04b6:start=1551621121816047113,finish=1551621121820694936,duration=4647823
travis_fold:end:after_failure.3
travis_fold:start:after_failure.4
travis_time:start:022a5730
$ ln -s . checkout && for CORE in obj/cores/core.*; do EXE=$(echo $CORE | sed 's|obj/cores/core\.[0-9]*\.!checkout!\(.*\)|\1|;y|!|/|'); if [ -f "$EXE" ]; then printf travis_fold":start:crashlog\n\033[31;1m%s\033[0m\n" "$CORE"; gdb --batch -q -c "$CORE" "$EXE" -iex 'set auto-load off' -iex 'dir src/' -iex 'set sysroot .' -ex bt -ex q; echo travis_fold":"end:crashlog; fi; done || true
travis_fold:end:after_failure.4
travis_fold:start:after_failure.5
travis_time:start:071f111a
travis_time:start:071f111a
$ cat ./obj/build/x86_64-unknown-linux-gnu/native/asan/build/lib/asan/clang_rt.asan-dynamic-i386.vers || true
cat: ./obj/build/x86_64-unknown-linux-gnu/native/asan/build/lib/asan/clang_rt.asan-dynamic-i386.vers: No such file or directory
travis_fold:end:after_failure.5
travis_fold:start:after_failure.6
travis_time:start:046dd03f
$ dmesg | grep -i kill

I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact @TimNN. (Feature Requests)

@Xanewok
Copy link
Member Author

Xanewok commented Mar 3, 2019

compiletest is fixed now, bumping Clippy to include the fix updating this dependency: rust-lang/rust-clippy#3838

@Xanewok
Copy link
Member Author

Xanewok commented Mar 3, 2019

Tested locally and both Clippy and RLS successfully compile now.
Bumping prio in hope of it making to the next nightly.

r? @Xanewok
@bors r+ p=1

@bors
Copy link
Contributor

bors commented Mar 3, 2019

📌 Commit 2254d74e85a40cee0117120e44903a3f46e8cbc5 has been approved by Xanewok

@rust-highfive rust-highfive assigned Xanewok and unassigned oli-obk Mar 3, 2019
@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 3, 2019
@bors
Copy link
Contributor

bors commented Mar 3, 2019

🔒 Merge conflict

This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again.

How do I rebase?

Assuming self is your fork and upstream is this repository, you can resolve the conflict following these steps:

  1. git checkout update-clippy (switch to your branch)
  2. git fetch upstream master (retrieve the latest master)
  3. git rebase upstream/master -p (rebase on top of it)
  4. Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
  5. git push self update-clippy --force-with-lease (update this PR)

You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial.

Please avoid the "Resolve conflicts" button on GitHub. It uses git merge instead of git rebase which makes the PR commit history more difficult to read.

Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Cargo.lock conflict is handled during merge and rebase. This is normal, and you should still perform step 5 to update this PR.

Error message
warning: Cannot merge binary files: Cargo.lock (HEAD vs. heads/homu-tmp)
Auto-merging Cargo.lock
CONFLICT (content): Merge conflict in Cargo.lock
Automatic merge failed; fix conflicts and then commit the result.

@bors bors added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Mar 3, 2019
@Xanewok
Copy link
Member Author

Xanewok commented Mar 3, 2019

@bors r+

@bors
Copy link
Contributor

bors commented Mar 3, 2019

📌 Commit d9afb40ed973ade3cff31b298c5014597c7de1c9 has been approved by Xanewok

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Mar 3, 2019
@bors
Copy link
Contributor

bors commented Mar 3, 2019

🔒 Merge conflict

This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again.

How do I rebase?

Assuming self is your fork and upstream is this repository, you can resolve the conflict following these steps:

  1. git checkout update-clippy (switch to your branch)
  2. git fetch upstream master (retrieve the latest master)
  3. git rebase upstream/master -p (rebase on top of it)
  4. Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
  5. git push self update-clippy --force-with-lease (update this PR)

You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial.

Please avoid the "Resolve conflicts" button on GitHub. It uses git merge instead of git rebase which makes the PR commit history more difficult to read.

Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Cargo.lock conflict is handled during merge and rebase. This is normal, and you should still perform step 5 to update this PR.

Error message
warning: Cannot merge binary files: Cargo.lock (HEAD vs. heads/homu-tmp)
Auto-merging Cargo.lock
CONFLICT (content): Merge conflict in Cargo.lock
Automatic merge failed; fix conflicts and then commit the result.

@bors bors added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Mar 3, 2019
@Xanewok
Copy link
Member Author

Xanewok commented Mar 3, 2019

@bors r+

@bors
Copy link
Contributor

bors commented Mar 3, 2019

📌 Commit 594e261 has been approved by Xanewok

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Mar 3, 2019
@bors
Copy link
Contributor

bors commented Mar 4, 2019

⌛ Testing commit 594e261 with merge 9261088...

bors added a commit that referenced this pull request Mar 4, 2019
Update Clippy

Should fix the fallout caused by #58321 (still testing it locally).

r? @oli-obk
@bors
Copy link
Contributor

bors commented Mar 4, 2019

☀️ Test successful - checks-travis, status-appveyor
Approved by: Xanewok
Pushing 9261088 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Mar 4, 2019
@bors bors merged commit 594e261 into rust-lang:master Mar 4, 2019
@rust-highfive
Copy link
Collaborator

📣 Toolstate changed by #58807!

Tested on commit 9261088.
Direct link to PR: #58807

🎉 clippy-driver on windows: build-fail → test-pass (cc @Manishearth @llogiq @mcarton @oli-obk @phansch, @rust-lang/infra).
🎉 clippy-driver on linux: build-fail → test-pass (cc @Manishearth @llogiq @mcarton @oli-obk @phansch, @rust-lang/infra).
🎉 rls on windows: build-fail → test-pass (cc @nrc @Xanewok, @rust-lang/infra).
🎉 rls on linux: build-fail → test-pass (cc @nrc @Xanewok, @rust-lang/infra).

rust-highfive added a commit to rust-lang-nursery/rust-toolstate that referenced this pull request Mar 4, 2019
Tested on commit rust-lang/rust@9261088.
Direct link to PR: <rust-lang/rust#58807>

🎉 clippy-driver on windows: build-fail → test-pass (cc @Manishearth @llogiq @mcarton @oli-obk @phansch, @rust-lang/infra).
🎉 clippy-driver on linux: build-fail → test-pass (cc @Manishearth @llogiq @mcarton @oli-obk @phansch, @rust-lang/infra).
🎉 rls on windows: build-fail → test-pass (cc @nrc @Xanewok, @rust-lang/infra).
🎉 rls on linux: build-fail → test-pass (cc @nrc @Xanewok, @rust-lang/infra).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants