Uh oh!
There was an error while loading. Please reload this page.
Async fn resume after completion - #66321
Conversation
rust-highfive
commented
Nov 12, 2019
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @zackmdavis (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
rust-highfive
commented
Nov 12, 2019
The job Click to expand the log.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 |
b585d99 to
238e604Comparerust-highfive
commented
Nov 12, 2019
The job Click to expand the log.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 |
Hi, this is my first rust compiler PR so I may need a little guidance. Been following the excellent documentation up to this point. Just a few questions:
There are more questions in the FIXME comments in the code itself. I will remove them once I have figured out what to do about them. Thanks, David. |
Uh oh!
There was an error while loading. Please reload this page.
gilescope
commented
Nov 13, 2019
Looks reasonable to me. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
bors
commented
Nov 14, 2019
☔ The latest upstream changes (presumably #66233) made this pull request unmergeable. Please resolve the merge conflicts. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Centril
commented
Nov 14, 2019
r? @oli-obk |
Ping from triage: |
rust-highfive
commented
Nov 25, 2019
The job Click to expand the log.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 |
99565e1 to
0b1e532Comparerust-highfive
commented
Nov 25, 2019
The job Click to expand the log.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 |
ninjasource
commented
Nov 26, 2019
Hi John, |
rust-highfive
commented
Nov 26, 2019
The job Click to expand the log.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 |
Uh oh!
There was an error while loading. Please reload this page.
oli-obk
commented
Nov 28, 2019
Hmm... I don't actually know how to run wasm tests. I don't even know who to ping. You can ask on zulip in the #compiler stream or on discord in the #compiler channel |
ninjasource
commented
Nov 29, 2019
Thanks @oli-obk, I got a response from @eddyb on Zulip and managed to run the ui tests against the wasm32-unknown-unknown target. The tests ran to completion but a third of all the tests failed so maybe you can't run them like this. Despite this I think that its worth giving the auto merge another go. I took a look at the other async tests and they all used edition:2018 instead of the compiler flags I used so I recon that that will fix the problem. I updated my tests to use edition:2018. |
eddyb
commented
Nov 29, 2019
@bors r=oli-obk |
bors
commented
Nov 29, 2019
📌 Commit 6531ba8 has been approved by |
bors
commented
Nov 29, 2019
…r=oli-obk Async fn resume after completion #65419 -- Attempting to run an async fn after completion mentions generators Not yet ready for review - work in progress Just need to run the tests on a proper build server
rust-highfive
commented
Nov 29, 2019
The job Click to expand the log.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 |
bors
commented
Nov 29, 2019
💔 Test failed - checks-azure |
| // be talking about `async fn`s instead. | ||
| // run-fail | ||
| // error-pattern: thread 'main' panicked at '`async fn` resumed after completion' |
There was a problem hiding this comment.
So... the error is RuntimeError: unreachable. Check whether any tests check for that error pattern, or if there are any wasm panic tests and how to check them. I think it would also be OK to just add // ignore-wasm to these tests if there's no way to specify different error patterns for different platforms
There was a problem hiding this comment.
(Assuming that the ignore-wasm comment is how this is done.) Search for it in the test suite, if it exists, that's it, if not, find out how to disable tests on wasm by searching for "wasm"
There was a problem hiding this comment.
The reason it's OK to disable the tests on wasm is that here we only want to see a specific panic message. We have tests to see that panicking in general works, so assuming panicking works and the tests work on most platforms, there's basically no way they'd be broken on wasm. Wasn't just generally doesn't show the panic message, but that's not something you need to solve in this PR
eddyb
commented
Nov 29, 2019
cc @rust-lang/wg-wasm See #66321 (comment) - is it possible to get panic messages from wasm, during testing? I assume |
Thanks @oli-obk and @eddyb. I have added If my latest checkin fails then can I suggest that the tests be moved back to |
Pauan
commented
Nov 29, 2019
@eddyb For raw Wasm I'm not aware of anything, but for Wasm running in JS environments there is So maybe you could use |
oli-obk
commented
Nov 29, 2019
bors
commented
Nov 29, 2019
📌 Commit 851492c has been approved by |
bors
commented
Nov 29, 2019
…r=oli-obk Async fn resume after completion #65419 -- Attempting to run an async fn after completion mentions generators Not yet ready for review - work in progress Just need to run the tests on a proper build server
bors
commented
Nov 29, 2019
☀️ Test successful - checks-azure |
#65419 -- Attempting to run an async fn after completion mentions generators
Not yet ready for review - work in progress
Just need to run the tests on a proper build server