-
Notifications
You must be signed in to change notification settings - Fork 14.1k
[EXPERIMENTAL] Test failure investigation #139561
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
Closed
Closed
Changes from 1 commit
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
89a42d6
Feed HIR for by-move coroutine body def, since the inliner tries to r…
compiler-errors b05f70b
Add `iter` macro (movable generator)
oli-obk 38ce680
Make `iter` a builtin macro
oli-obk e84ccac
Make diagnostics know about more coro closures than async closures
oli-obk 4806ac6
Use yield_expr feature for iter_macro tests
eholk b770e51
Remove support for expr-only yield!
eholk 3eb7b78
Update and fix tests
eholk 2e6e242
Add a test for iterators that capture but don't lend
eholk 69a65cd
Add some tests to make sure iter macros do not accidentally become as…
eholk 5309dbd
Remove AsyncFn* impls from gnerator closures
eholk 3d5a21a
Update error message for const_gen_fn.rs
eholk 676bf46
Gate const coroutines better
eholk 51d09de
Add FIXME about const coroutine feature
eholk 85243d3
Fix CI test failure due to `diagnostic-width`
traviscross 121a5ae
[EXPERIMENTAL] Try `//@ remap-src-base`
jieyouxu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,54 @@ | ||
| error[E0277]: the trait bound `{gen closure@$DIR/iter-macro-not-async-closure.rs:24:21: 24:28}: AsyncFnOnce()` is not satisfied | ||
| --> $DIR/iter-macro-not-async-closure.rs:30:34 | ||
| | | ||
| LL | let x = pin!(call_async_once(f)); | ||
| | --------------- ^ the trait `AsyncFnOnce()` is not implemented for `{gen closure@$DIR/iter-macro-not-async-closure.rs:24:21: 24:28}` | ||
| | | | ||
| | required by a bound introduced by this call | ||
| | | ||
| note: required by a bound in `call_async_once` | ||
| --> $DIR/iter-macro-not-async-closure.rs:19:34 | ||
| | | ||
| LL | async fn call_async_once(f: impl AsyncFnOnce()) { | ||
| | ^^^^^^^^^^^^^ required by this bound in `call_async_once` | ||
|
|
||
| error[E0277]: the trait bound `{gen closure@$DIR/iter-macro-not-async-closure.rs:24:21: 24:28}: AsyncFnOnce()` is not satisfied | ||
| --> $DIR/iter-macro-not-async-closure.rs:30:18 | ||
| | | ||
| LL | let x = pin!(call_async_once(f)); | ||
| | ^^^^^^^^^^^^^^^^^^ the trait `AsyncFnOnce()` is not implemented for `{gen closure@$DIR/iter-macro-not-async-closure.rs:24:21: 24:28}` | ||
| | | ||
| note: required by a bound in `call_async_once` | ||
| --> $DIR/iter-macro-not-async-closure.rs:19:34 | ||
| | | ||
| LL | async fn call_async_once(f: impl AsyncFnOnce()) { | ||
| | ^^^^^^^^^^^^^ required by this bound in `call_async_once` | ||
|
|
||
| error[E0277]: the trait bound `{gen closure@$DIR/iter-macro-not-async-closure.rs:24:21: 24:28}: AsyncFnOnce()` is not satisfied | ||
| --> $DIR/iter-macro-not-async-closure.rs:30:13 | ||
| | | ||
| LL | let x = pin!(call_async_once(f)); | ||
| | ^^^^^^^^^^^^^^^^^^^^^^^^ the trait `AsyncFnOnce()` is not implemented for `{gen closure@$DIR/iter-macro-not-async-closure.rs:24:21: 24:28}` | ||
| | | ||
| note: required by a bound in `call_async_once` | ||
| --> $DIR/iter-macro-not-async-closure.rs:19:34 | ||
| | | ||
| LL | async fn call_async_once(f: impl AsyncFnOnce()) { | ||
| | ^^^^^^^^^^^^^ required by this bound in `call_async_once` | ||
| = note: this error originates in the macro `pin` (in Nightly builds, run with -Z macro-backtrace for more info) | ||
|
|
||
| error[E0277]: the trait bound `{gen closure@$DIR/iter-macro-not-async-closure.rs:24:21: 24:28}: AsyncFnOnce()` is not satisfied | ||
| --> $DIR/iter-macro-not-async-closure.rs:34:5 | ||
| | | ||
| LL | x.poll(&mut Context::from_waker(Waker::noop())); | ||
| | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `AsyncFnOnce()` is not implemented for `{gen closure@$DIR/iter-macro-not-async-closure.rs:24:21: 24:28}` | ||
| | | ||
| note: required by a bound in `call_async_once` | ||
| --> $DIR/iter-macro-not-async-closure.rs:19:34 | ||
| | | ||
| LL | async fn call_async_once(f: impl AsyncFnOnce()) { | ||
| | ^^^^^^^^^^^^^ required by this bound in `call_async_once` | ||
|
|
||
| error: aborting due to 4 previous errors | ||
|
|
||
| For more information about this error, try `rustc --explain E0277`. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks almost like the test intentionally wants to cover different widths?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Yes, I'm just checking if the original version of the test passes without manually specifying diag width, since it failed in CI but not locally)