Skip to content

lute test produces profoundly uninformative errors #1305

Description

@nnullcolumn

currently, errors in individual test files will result in something like:

Results: 540 passed, 0 failed of 540

Worker failures:

  WORKER <error message>

..with no stacktrace. so, if you have a bad error message or something and it happens in the root of a file, gg

on direct error calls there's a click to the path of the error, but e.g. require affords nothing like that. plus the direct path might just be some logger util

Activity

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

    bugSomething isn't workingcliThe lute command-line interface

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions