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

Rollup of 15 pull requests #65139

Closed
wants to merge 35 commits into from
Closed

Conversation

tmandry
Copy link
Member

@tmandry tmandry commented Oct 5, 2019

Successful merges:

Failed merges:

r? @ghost

SimonSapin and others added 30 commits September 23, 2019 17:14
The tracking issue rust-lang#50264
still has unresolved question for the corresponding `Result` methods.
This is a stylistic change to libstd to reduce the number of checks of
`feature = "backtrace"` now that we unconditionally depend on the
`backtrace` crate and rely on it having an empty implementation.
otherwise.
Still debating if this is the right approach
Co-Authored-By: Pietro Albini <pietro@pietroalbini.org>
visit_statement default definition does just this, there's no need to
redefine it.
It has been fully disabled by default since rust-lang#54639.
This commit makes the `improper_ctype` lint trigger for non-exhaustive
types when those types aren't defined in the current crate.

Signed-off-by: David Wood <david@davidtw.co>
Stabilize `Option::as_deref` and `Option::as_deref_mut`

The tracking issue rust-lang#50264 still has unresolved question for the corresponding `Result` methods.
…r=sfackler

std: Reduce checks for `feature = "backtrace"`

This is a stylistic change to libstd to reduce the number of checks of
`feature = "backtrace"` now that we unconditionally depend on the
`backtrace` crate and rely on it having an empty implementation.
otherwise.
Do not ICE when dereferencing non-Copy raw pointer

CC rust-lang#52262. Confirmed to remove the unnecessary ICE, but without a repro case.
…by-anyone, r=nikomatsakis

permit asyncawait-ondeck to be added by anyone

Still debating if this is the right approach

but r? @pietroalbini to check the format
…olymorphic_promoted_mir, r=oli-obk

[const-prop] Fix ICE when trying to eval polymorphic promoted MIR

Fixes rust-lang#64908

r? @oli-obk
cc @nikomatsakis @pnkfelix
…-err-codes, r=varkor

Sort error codes in librustc_passes

This is just a little cleanup.
…r=Centril

Allow unused attributes to avoid incremental bug

cc rust-lang#65023

This isn't labeled as fixing that issue because it's not really a fix, just a patch.
Fix lonely backtick

That backtick won't be sad anymore
…i-obk

Remove unneeded visit_statement definition

r? @oli-obk
…=rkruppe

Update the documented default of -Z mutable-noalias

It has been fully disabled by default since rust-lang#54639.
…ebank

Account for macro invocation in `let mut $pat` diagnostic.

Fixes rust-lang#65122.

r? @estebank
Replace some instances of `as *[const | mut] _` with `.cast()`

While in `codegen_llvm`, noticed some places for the recent `pointer::cast` method.
Fix typo on `now()` comments

Fix typo, update words, and remove some redundant word.
Also rustfmt on the rest of the file (hope this is okay :)

revival of rust-lang#61433

r? @kennytm
… r=petrochenkov

lint: extern non-exhaustive types are improper

This PR makes the `improper_ctype` lint trigger for non-exhaustive types when those types aren't defined in the current crate, as per [this comment](rust-lang#44109 (comment)).

cc @Centril
@tmandry
Copy link
Member Author

tmandry commented Oct 5, 2019

@bors r+ p=15 rollup=never

@bors
Copy link
Contributor

bors commented Oct 5, 2019

📌 Commit 4fd8f37 has been approved by tmandry

@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Oct 5, 2019
@bors
Copy link
Contributor

bors commented Oct 5, 2019

⌛ Testing commit 4fd8f37 with merge 2d4822bdb9bd2379956d7ed331545784850957bf...

@tmandry tmandry added the rollup A PR which is a rollup label Oct 5, 2019
@bors
Copy link
Contributor

bors commented Oct 6, 2019

💥 Test timed out

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Oct 6, 2019
@tmandry
Copy link
Member Author

tmandry commented Oct 6, 2019

Looks like this succeeded, but timed out... @bors retry

@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 Oct 6, 2019
@bors
Copy link
Contributor

bors commented Oct 6, 2019

⌛ Testing commit 4fd8f37 with merge 4566201c8294fd960504e7725afca5392ef7bcea...

@tmandry tmandry added the A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) label Oct 6, 2019
@alex
Copy link
Member

alex commented Oct 6, 2019

@tmandry FWIW, it seems the last several bors builds have all failed on asmjs timeouts. The last commit to land was emscripten related, so I think this is not a coincidence.

@Aaron1011
Copy link
Member

Would it be possible to increase the Bors timeout, given that this didn't actually hit any Azure timeouts?

@tmandry
Copy link
Member Author

tmandry commented Oct 6, 2019

@alex thanks for pointing that out. I've reverted the emscripten change and am going to close this rollup in favor of another that includes the revert.

@bors retry yielding to #65152
@bors r-

@tmandry
Copy link
Member Author

tmandry commented Oct 6, 2019

@bors r-

@tmandry tmandry closed this Oct 6, 2019
@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 Oct 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) rollup A PR which is a rollup S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author.
Projects
None yet
Development

Successfully merging this pull request may close these issues.