v2-test in master should ignore --test-option[s] from the hash

[fommil]

in any project with tasty, with cabal 2.5, running this

cabal v2-test -O0 --test-options="--pattern Foo"

followed by

cabal v2-test -O0 --test-options="--pattern Bar"

will result in trying to recompile everything.

It looks like test-option and test-options are being included in the hash.

[anka-213]

Does anyone know of a workaround for this problem? It's getting pretty frustrating.

[fommil]

I invoke test binaries directly with run and just pretend test doesn't exist.

cabal run tasty -- --pattern Foo
cabal run tasty -- --pattern Bar

doesn't recompile

[anka-213]

@fommil That almost works, but now the test-suite fails to execute the main executable ghcide and other tools which are included via build-tool-depends:

test-suite ghcide-tests
    build-tool-depends:
        ghcide:ghcide,
        ghcide:ghcide-test-preprocessor,
        implicit-hie:gen-hie
    ...

$ cabal run ghcide-tests
Up to date
cabal get -v1 Cabal-3.2.0.0 -d bench/example
ghcide
  diagnostics
    haddock parse error:          FAIL
      Exception: ghcide: createProcess: runInteractiveProcess: exec: does not exist (No such file or directory)
...
    hover after edit:             FAIL
      Exception: gen-hie: createProcess: runInteractiveProcess: exec: does not exist (No such file or directory)

Is there some alternative runtime-tool-depends or another way to make this work?