Closed geekosaur closed 1 month ago
Should validate.sh
point to a default config file via CABAL_CONFIG
, or does it need to use some other mechanism to avoid overriding test-specific config files?
dunno but perhaps if you do something wrong and override the test-specific configs it will fail horribly?..
It looks like IntegrationTests2
already has a default cabal config; it's just not using it, as far as I can tell, or at least isn't using it everywhere it needs to be used. I'm thinking that needs to be moved into validate.sh
.
Describe the bug If my local cabal configuration contains
documentation: True
, runningvalidate.sh
locally fails withValidation succeeds if I comment out the
documentation
directive in my local config.To Reproduce Steps to reproduce the behavior:
Expected behavior Validation should succeed regardless of the local setting of
documentation
.System information
cabal
master
HEAD
as of 2024-07-08,ghc
9.6.6