Skip to content

[Wasm] Tracking active test failures  #38422

Closed

Description

@steveisok

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

Activity

  1. added this to the 5.0.0 milestone on Jun 26, 2020
  2. Dotnet-GitSync-Bot commented on Jun 26, 2020

    @Dotnet-GitSync-Bot
    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.

  3. removed
    untriagedNew issue has not been triaged by the area owner
    on Jun 26, 2020
  4. added
    trackingThis issue is tracking the completion of other related issues.
    on Jul 1, 2020
  5. safern commented on Jul 8, 2020

    @safern
    Member

    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

  6. akoeplinger commented on Sep 3, 2020

    @akoeplinger
    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

  7. modified the milestones: 5.0.0, 6.0.0 on Sep 3, 2020
  8. lewing commented on Jul 31, 2021

    @lewing
    Member

    @steveisok what is the state of this now?

  9. steveisok commented on Jul 31, 2021

    @steveisok
    MemberAuthor

    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.

  10. lewing commented on Jul 31, 2021

    @lewing
    Member

    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

  11. ghost locked as resolved and limited conversation to collaborators on Aug 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    arch-wasmWebAssembly architecturearea-MetatrackingThis issue is tracking the completion of other related issues.

    Type

    No type

    Projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions