Skip to content
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.

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

testsuite: Be explicit about runtime test dependencies #9439

Merged
merged 1 commit into from
Nov 16, 2023

Commits on Nov 16, 2023

  1. testsuite: Be explicit about runtime test dependencies

    Issue haskell#8356 reports occasional errors from running the testsuite about
    multiple package versions available. This stems from the invokation of
    `runghc` not being explicit about all dependencies of the testsuite.
    
    The solution is provide a component in the cabal file which is explicit
    about which packages the tests can depend on. This component has a
    build-depends section which lists all the dependencies that the tests
    require.
    
    It would be better if this component was a library component but we
    can't do this with a Custom setup because of limitations to do with
    per-component builds.
    
    Then we also enable `-hide-all-packages`, so the dependency will not be
    available if it is not explicitly listed as a dependency.
    
    You could also imagine a future where the Setup.hs script found the test
    files and compiled a single executable which would run all the tests,
    rather than invoking runghc on each one individually.
    
    Fixes haskell#8356
    mpickering authored and Mikolaj committed Nov 16, 2023
    Configuration menu
    Copy the full SHA
    5c2286a View commit details
    Browse the repository at this point in the history