Skip to content

hangs on failing test #38

@HansHammel

Description

@HansHammel

It seems that a failing test is no recognized (exit code problem!?) causing the job progress to freeze, blocking/breaking the job queue. How about a timeout hot fix? node 6.9.1 npm 3.10.8 windows 10 64bit latest strider + available updates

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions