`cabal run -O0` seems to use wrong executable

[sjakobi]

While working on https://github.com/dhall-lang/dhall-haskell, I've run into a weird issue where cabal run -O0 seems to use an executable that doesn't incorporate the latest source changes. Without the -O0 flag, cabal run behaves as expected.

Is this a known issue?

System information

$ cabal --version
cabal-install version 3.2.0.0
compiled using version 3.2.0.0 of the Cabal library 

[sjakobi]

Hmm. After switching between cabal run -O0 -- dhall:dhall format and cabal run -O0 dhall:dhall format, the issue has gone away. Very weird.

EDIT: No, sorry.

[sjakobi]

I've run into this again while working on haskell-unordered-containers/unordered-containers#435. I was using cabal run tests -O0 -- --quickcheck-tests 100000 -p union to test my code and getting somewhat mystified that I didn't get any test failures. Subsequent runs with cabal test -O1 finally revealed the bugs. After running cabal test -O0, cabal run tests -O0 started showing the test failures too.

There was a ghcid process running in the same project. Could this have confused cabal in some way?!

In any case this makes me very hesitant to rely on cabal run going forward, which is sad, because I really like its ergonomics!

$ cabal --version
cabal-install version 3.6.2.0
compiled using version 3.6.2.0 of the Cabal library 

[Mikolaj]

I have no idea how the hack of cabal run in place of cabal test actually works. Perhaps it fails to consider some dependencies. I'm afraid, for now,

cabal test tests -O0 --test-options='--quickcheck-tests 100000 -p "Short CI MNIST tests"'

may be the only trustworthy option. @pranaysashank in #8093 attempts to make it less fragile, but IIRC we hit some Windows eccentricity problems.