cabal test doesn't change to package directory

[phadej]

See https://github.com/phadej/regression-simple/actions/runs/12600704188/job/35120309804?pr=14

I'm puzzled what's happening, as I cannot reproduce that locally. Locally cabal test changes directory.

The important part of log:

["--working-dir=/__w/regression-simple/regression-simple/unpacked/regression-simple-0.2.2","test","--verbose=2","--builddir=/__w/regression-simple/regression-simple/dist-newstyle/build/x86_64-linux/ghc-8.8.4/regression-simple-0.2.2/t/regression-simple-tests","--log=$pkgid-$test-suite.log","--machine-log=$pkgid.log","--show-details=direct","regression-simple-tests"]
Reading installed packages...
Running: /github/home/.ghcup/ghc/8.8.4/bin/ghc-pkg-8.8.4 dump --global -v0
Running: /github/home/.ghcup/ghc/8.8.4/bin/ghc-pkg-8.8.4 dump '--package-db=/github/home/.cabal/store/ghc-8.8.4/package.db' -v0
Running: /github/home/.ghcup/ghc/8.8.4/bin/ghc-pkg-8.8.4 dump '--package-db=/__w/regression-simple/regression-simple/dist-newstyle/packagedb/ghc-8.8.4' -v0
Running: /github/home/.ghcup/ghc/8.8.4/bin/ghc-pkg-8.8.4 dump '--package-db=/__w/regression-simple/regression-simple/dist-newstyle/build/x86_64-linux/ghc-8.8.4/regression-simple-0.2.2/t/regression-simple-tests/package.conf.inplace' -v0
Running: /github/home/.ghcup/ghc/8.8.4/bin/ghc --print-libdir -hide-all-packages '+RTS' -M3G -RTS '-Werror=missing-methods'
Running 1 test suites...
Test suite regression-simple-tests: RUNNING...
Running: /__w/regression-simple/regression-simple/dist-newstyle/build/x86_64-linux/ghc-8.8.4/regression-simple-0.2.2/t/regression-simple-tests/build/regression-simple-tests/regression-simple-tests
"/__w/regression-simple/regression-simple"

the --working-dir argument is the package directory, but when program is run, it's not respected, the test suite starts with

getCurrentDirectory >>= print

[phadej]

I tried with cabal-install-3.12.1.0, and that works. So some change in 3.14 makes CI fail.

[phadej]

Locally I see

Running: /opt/ghcup/.ghcup/bin/cabal-3.14.1.0 act-as-setup '--build-type=Simple' -- '--working-dir=/codetmp/p/u/regression-simple-0.2.1' test '--verbose=2' '--builddir=/codetmp/p/dist-newstyle/build/x86_64-linux/ghc-8.8.4/regression-simple-0.2.1/t/regression-simple-tests' '--log=$pkgid-$test-suite.log' '--machine-log=$pkgid.log' '--show-details=direct' regression-simple-tests

but on CI I see

Using internal setup method with build-type Simple and args:
["--working-dir=/__w/regression-simple/regression-simple/unpacked/regression-simple-0.2.2","test","--verbose=2","--builddir=/__w/regression-simple/regression-simple/dist-newstyle/build/x86_64-linux/ghc-9.8.4/regression-simple-0.2.2/t/regression-simple-tests","--log=$pkgid-$test-suite.log","--machine-log=$pkgid.log","--show-details=direct","regression-simple-tests"]

Now I can reproduce this locally, if I add -j1 argument, then cabal-install uses internal setup method and --working-dir directory change fails.

[phadej]

I suspect this is bug is introduced in 7b90583. Ping @sheaf.

Currently cabal-install-3.14 is unusable in my CI setups without workarounds.

[phadej]

This issue is causing problems with aeson test-suite.

[andreasabel]

This seems in particular to affect haskell-ci generated workflows with a cabal testsuite that accesses files.
Another example of such failure seems to be: https://github.com/hackage-trustees/hackage-cli/actions/runs/12653979112/job/35260731276?pr=74#step:23:32

[mpickering]

I have been assigned to look into this.