Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • GHC GHC
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 4,860
    • Issues 4,860
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 456
    • Merge requests 456
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Glasgow Haskell Compiler
  • GHCGHC
  • Issues
  • #19072
Closed
Open
Created Dec 16, 2020 by Ben Gamari@bgamari🐢Maintainer

Hadrian test looks a state of tree to determine whether documentation is available

hadrian test exhibits an rather surprising behavior. Namely, this:

hadrian/build-cabal
hadrian/build-cabal test

and

hadrian/build-cabal
hadrian/build-cabal docs
hadrian/build-cabal test

are not equivalent.

The reason is that Hadrian does not look at the build configuration to determine whether haddock is available; rather, it checks whether the build documentation files happen to exist. Surprisingly, these are not build during the default build. This means that tests which are marked as req_haddock do not build unless you first explicitly build the docs target. This took far too long to discover.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking