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

Running `cry quick-test` without building first causes the first test to spuriously fail #1817

Open

danmatichuk opened this issue Feb 28, 2025 · 0 comments

Labels

bug test-framework

Contributor

danmatichuk commented Feb 28, 2025

It seems like the test tool is erroneously capturing the stdout of cabal when matching against the stdout of the first test:

./cry quick-test
Running quick tests
tests:
  docstrings:
    T01.icry: [Failed]
0a1,40
> 
> src/Cryptol/ModuleSystem/Binds.hs:338:3: warning: [GHC-62161] [-Wincomplete-uni-patterns]
>     Pattern match(es) are non-exhaustive
>     In a pattern binding:
>         Patterns of type ‘Maybe ModPath’ not matched: Nothing

The text was updated successfully, but these errors were encountered:

danmatichuk added bug test-framework labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment