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.

Sign up for GitHub

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

Jump to bottom

[Wasm] Tracking active test failures #38422

Closed
95 of 99 tasks
steveisok opened this issue Jun 26, 2020 · 6 comments
Closed
95 of 99 tasks

[Wasm] Tracking active test failures #38422

steveisok opened this issue Jun 26, 2020 · 6 comments
Labels
arch-wasm WebAssembly architecture area-Meta tracking This issue is tracking the completion of other related issues.
Milestone
6.0.0

Comments

@steveisok
Copy link
Member

steveisok commented Jun 26, 2020 •
edited by mdh1418
Loading

We began running tests for wasm on CI, however not all test suites currently pass. This issue tracks what's failing:

OOB = out of box library

Suites that contain 1 or more failures

Suites that do not produce results

These tests most likely contain >= 1 thread related failures and need to be skipped

Flaky suites
@steveisok steveisok added the arch-wasm WebAssembly architecture label Jun 26, 2020
@steveisok steveisok added this to the 5.0.0 milestone Jun 26, 2020
@Dotnet-GitSync-Bot
Copy link
Collaborator

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Jun 26, 2020
@steveisok steveisok removed the untriaged New issue has not been triaged by the area owner label Jun 26, 2020
This was referenced Jun 29, 2020
Merged
Merged
@MaximLipnin MaximLipnin mentioned this issue Jul 1, 2020
Merged
@marek-safar marek-safar added the tracking This issue is tracking the completion of other related issues. label Jul 1, 2020
@mdh1418 mdh1418 mentioned this issue Jul 1, 2020
Merged
This was referenced Jul 3, 2020
Merged
Merged
This was referenced Jul 6, 2020
Merged
Merged
This was referenced Jul 7, 2020
Merged
Merged
Merged
@akoeplinger akoeplinger mentioned this issue Jul 8, 2020
Merged
@safern
Copy link
Member

safern commented Jul 8, 2020

System.Globalization.CalendarsWithConfigSwitch.Tests
System.Globalization.Calendars.Tests
System.Globalization.Extensions.Tests
System.Globalization.Tests

Synced up with @steveisok and @tarekgh and it makes sense to keep them disabled from CI until ICU is turned on and then we can adjust/skip tests based on the ICU globalization story for WASM. If we want to get more test coverage when running on Invariant mode, we can add those tests to System.Globalization/tests/Invariant/Invariant.Tests.csproj

This was referenced Jul 9, 2020
Merged
Merged
@mdh1418 mdh1418 mentioned this issue Jul 9, 2020
Merged
@MaximLipnin MaximLipnin mentioned this issue Jul 9, 2020
Merged
This was referenced Jul 9, 2020
Merged
Merged
@mdh1418 mdh1418 mentioned this issue Jul 10, 2020
Merged
@MaximLipnin MaximLipnin mentioned this issue Jul 13, 2020
Merged
This was referenced Jul 21, 2020
Merged
Merged
Merged
@safern safern mentioned this issue Jul 23, 2020
Merged
@MaximLipnin MaximLipnin mentioned this issue Jul 23, 2020
Merged
@safern safern mentioned this issue Jul 23, 2020
Merged
This was referenced Jul 27, 2020
Merged
Merged
Jacksondr5 pushed a commit to Jacksondr5/runtime that referenced this issue Aug 10, 2020
@MaximLipnin @Jacksondr5
[wasm] Enable System.CodeDom.Tests test suite (dotnet#39626)
400175c 
Part of dotnet#38422.
@akoeplinger
Copy link
Member

There are still three test suites we need to enable and also take a look at the flaky System.Linq.Parallel.Tests, keeping it open and in 6.0

@akoeplinger akoeplinger reopened this Sep 3, 2020
@akoeplinger akoeplinger modified the milestones: 5.0.0, 6.0.0 Sep 3, 2020
@lewing
Copy link
Member

lewing commented Jul 31, 2021

@steveisok what is the state of this now?

@steveisok
Copy link
Member Author

Once you get runtimeconfig.json support, the calendar test should light up. Mostly good it looks like. Probably can close this and deal with the few remaining in another issue.

@lewing
Copy link
Member

lewing commented Jul 31, 2021

Once you get runtimeconfig.json support, the calendar test should light up. Mostly good it looks like. Probably can close this and deal with the few remaining in another issue.

yeah I think this is safe to close not that we are tracking the remaining work elsewhere

@lewing lewing closed this as completed Jul 31, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Aug 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
arch-wasm WebAssembly architecture area-Meta tracking This issue is tracking the completion of other related issues.
Projects
No open projects
Triage POD for Reflection, META, etc.
Status: Done
Milestone
6.0.0
Development

No branches or pull requests
6 participants
@lewing @marek-safar @steveisok @akoeplinger @safern @Dotnet-GitSync-Bot