Skip to content

dwds test flakiness #721

Description

@alan-knight

We've got a number of flaky tests, particularly on Travis. Windows is worse, but I see it even on Linux. For example
getStack / returns null if not paused
can return an empty stack rather than null. I think this indicates that the actual state was paused at isolate start. So probably a race condition.

Activity

  1. added
    type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
    P1A high priority bug; for example, a single project is unusable or has many test failures
    on Oct 15, 2019
  2. grouma commented on Oct 24, 2019

    @grouma
    Member

    Closing this as I'm told this is mostly resolved.

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

    P1A high priority bug; for example, a single project is unusable or has many test failurespackage:dwdstype-bugIncorrect behavior (everything from a crash to more subtle misbehavior)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions