-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Tar tests that interact with file assets do not work on Browser #69953
Comments
Tagging subscribers to this area: @dotnet/area-system-io Issue DetailsIn this PR resubmission I added the missing Browser target platform in the tests project, and the result was that the browser tests that need to read file assets do not work on WASM. Those test classes that read file assets will be topped with the ActiveIssue attribute and will be linked to this issue for future investigation, to unblock merging that PR. Here's an output example of one of the browser CI legs:
|
@carlossanlop you can surface files to the wasm app by using |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsIn this PR resubmission I added the missing Browser target platform in the tests project, and the result was that the browser tests that need to read file assets do not work on WASM. Those test classes that read file assets will be topped with the ActiveIssue attribute and will be linked to this issue for future investigation, to unblock merging that PR. Here's an output example of one of the browser CI legs:
|
In this PR resubmission I added the missing Browser target platform in the tests project, and the result was that the browser tests that need to read file assets do not work on WASM.
Those test classes that read file assets will be topped with the ActiveIssue attribute and will be linked to this issue for future investigation, to unblock merging that PR.
Log1, log2
Here's an output example of one of the browser CI legs:
The text was updated successfully, but these errors were encountered: