-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Fix Wasm async continuation stack walk #133995
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
Changes from all commits
e50a02c
b3b2ec9
f4d626b
c0b5d12
85afcea
3604189
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,10 @@ | ||
| <Project> | ||
| <PropertyGroup> | ||
| <!-- Mono does not support runtime async. Wasm tests must explicitly opt in after avoiding unsupported operations such as Task.Yield. --> | ||
| <!-- Mono does not support runtime async. Wasm tests must explicitly opt in after avoiding unsupported operations such as synchronous waits. --> | ||
| <DisableProjectBuild Condition="'$(RuntimeFlavor)' == 'mono' or ('$(TargetArchitecture)' == 'wasm' and '$(EnableRuntimeAsyncOnWasm)' != 'true')">true</DisableProjectBuild> | ||
| </PropertyGroup> | ||
| <ItemGroup Condition="'$(MSBuildProjectFullPath)' != '$(MSBuildThisFileDirectory)async.csproj'"> | ||
| <ProjectReference Include="$(TestLibraryProjectPath)" /> | ||
| </ItemGroup> | ||
| <Import Project="$([MSBuild]::GetPathOfFileAbove(Directory.Build.targets, $(MSBuildThisFileDirectory)..))" /> | ||
| </Project> |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,7 +7,7 @@ | |
|
|
||
| public class AwaitNotAsync | ||
| { | ||
| [Fact] | ||
| [ConditionalFact(typeof(TestLibrary.PlatformDetection), nameof(TestLibrary.PlatformDetection.IsMultithreadingSupported))] | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this really how we want to deal with this for wasm? I do not think it is very reasonable to have to mark all async tests this way if they don't finish synchronously....
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Browser has single thread.
The better way is to make the whole unit test method async and I'm not sure if some of the tests actually validate
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Yes, I agree. I think this requires work in the test generator to support
We may start and run async tasks in parallel, but I do not think any runtime async test should be validating
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @lewing could you please ask your copilot to do that as follow up?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I am working on it in #134042 |
||
| public static void TestEntryPoint() | ||
| { | ||
| AsyncEntryPoint().Wait(); | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.