Add a CI check of cabal.project.release?

[philderbeast]

I suspect that cabal.project.release is seldom touched. We might ensure that it is kept up-to-date by adding its build to CI with:

$ cabal build all \
  --enable-tests --enable-benchmarks --dry-run \
  --project-file=cabal.project.release \
  --index-state="hackage.haskell.org HEAD"

cabal/cabal.project.release

Lines 1 to 8 in 49e3d18

	packages: Cabal-syntax/
	packages: Cabal/
	packages: cabal-install-solver/
	packages: cabal-install/
	tests: False
	benchmarks: False
	optimization: True
	index-state: hackage.haskell.org 2023-10-13T10:16:13Z

On the master branch at 49e3d18:

$ cabal build all \
  --enable-tests --enable-benchmarks --dry-run \
  --project-file=cabal.project.release \
  --index-state="hackage.haskell.org HEAD"
Resolving dependencies...
Error: [Cabal-7107]
Could not resolve dependencies:
[__0] trying: cabal-install-3.11.0.0 (user goal)
[__1] trying: cabal-install:*test
[__2] unknown package: Cabal-described (dependency of cabal-install *test)
[__2] fail (backjumping, conflict set: Cabal-described, cabal-install, cabal-install:test)
After searching the rest of the dependency tree exhaustively,
these were the goals I've had most trouble fulfilling: cabal-install, cabal-install:test, Cabal-described

Originally posted by @philderbeast in #9565 (comment)

[philderbeast]

@ffaf1 sorry about the half-formed issue with wacky title. I fumbled, missed a key and hit enter.

[Mikolaj]

Yes, we definitely should. And if it builds with the same flags as the other CI builds, it should take almost no time (I hope the --project-file does not cause recompilation unless anything in the new project file does).

[ulysses4ever]

The failure in build is a more or less known one. There's a ticket to factor out tests out of the main packages so that they don't confuse people anymore.

[philderbeast]

I don't know what to do with this project. Should it be buildable if I --enable-tests and --enable-benchmarks from the command line even though it has these settings in the off position in the project?

cabal/cabal.project.release

Lines 5 to 6 in 381441f

	tests: False
	benchmarks: False

It does build without --enable-tests and without --enable-benchmarks:

$ cabal build all --dry-run --project-file=cabal.project.release --index-state="hackage.haskell.org HEAD"
Resolving dependencies...
Build profile: -w ghc-9.8.1 -O1
In order, the following would be built (use -v for more details):
 - Cabal-3.11.0.0 (lib) (file src/Distribution/PackageDescription/Check/Warning.hs changed)
 - hackage-security-0.6.2.4 (lib) (configuration changed)
 - cabal-install-solver-3.11.0.0 (lib) (configuration changed)
 - cabal-install-3.11.0.0 (lib) (configuration changed)
 - cabal-install-3.11.0.0 (exe:cabal) (configuration changed)

[philderbeast]

Thanks @ulysses4ever, I went hunting for that ticket but couldn't find it.

Theres' #5745 but that is about CI taking too long.

[ulysses4ever]

Yeah, my bad I should have looked it up before posting but it did prove to be tricky to look up.

• Separate remaining cabal tests into their own packages #8439