Problems running ghcide benchmarks

[qrilka]

Following the suggestion from @pepeiborra to use https://github.com/haskell/haskell-language-server/tree/master/ghcide/bench for checking out HLS performance I tried to run it using lsp-types as a smaller example (compared to Cabal) but could do that.

First I tried to make it run with Stack, after some tweaking of stack.yaml I got the build process starting up but it looks like -eventlog is not being passed somewhere as stracing shows the following message from GHC RTS:

ghcide: the flag -l-au requires the program to be built with -eventlog, -prof or -debug

Quick look didn't reveal a place how this could be fixed so I switched to cabal but using the shell.nix supplied with the project doesn't help as the benchmarks don't seem to be compatible with Nix. I get the following error in logs:

Error when calling cabal --builddir=/home/kirill/.cache/hie-bios/dist-lsp-types-1.0.0-5e8c96bd74e413bf187d2a4df02e9122 v2-exec --with-compiler /home/kirill/.cache/hie-bios/wrapper-13a09b18ea883dd377d59db5e821a86b ghc -v0 -- --print-libdir","","cabal: The program 'ghc' version >=7.0.1 is required but the version of\n/home/kirill/.cache/hie-bios/wrapper-13a09b18ea883dd377d59db5e821a86b could\nnot be determined.\n\n

After that I switched to GHC/cabal installed with ghcup (I use Ubuntu if that matters) and that forced me to drop ~/.cabal as Cabal doesn't appear to support this kind of switch. And in the end I get even more cryptic error in benchmark logs:

Failed to parse result of calling cabal  cabal: Internal error in target matching. It should always be possible to finda syntax that's sufficiently qualified to give an unambiguous match. However
when matching 'lib:lsp-types' we found lib:lsp-types (unknown-component) which
does not have an unambiguous syntax. The possible syntax and the targets they
match are as follows:
'lib:lsp-types' which matches lib:lsp-types (unknown-component),
:pkg:lib:lib:lib:file:lsp-types (unknown-file)

Am I doing anything wrong here and what is the proper way to run these benchmarks?

[pepeiborra]

What command line are you using? cabal bench ghcide is what I use

[qrilka]

I was using cabal bench ghcide --benchmark-options="lsp-types"

[pepeiborra]

Does cabal bench ghcide work for you? I don't think that lsp-types is a valid rule - you can see all the rules with --help

[qrilka]

I've taken in from targets shown by --help, i.e. from the following list:

Targets:
  - bench-results/binaries/*/commitid
  - bench-results/binaries/HEAD/ghcide
  - bench-results/binaries/HEAD/ghc.path
  - bench-results/binaries/*/ghcide
  - bench-results/binaries/*/ghc.path
  - bench-results/binaries/*/*.warmup
  - bench-results/*/*/*/*.csv
  - bench-results/*/*/*/*.gcStats.log
  - bench-results/*/*/*/*.output.log
  - bench-results/*/*/*/*.eventlog
  - bench-results/*/*/*/*.hp
  - bench-results/*/*/*/results.csv
  - bench-results/*/*/results.csv
  - bench-results/*/results.csv
  - bench-results/*/*/*/*.svg
  - bench-results/*/*/*/*.diff.svg
  - bench-results/*/*/*.svg
  - bench-results/*/*/*/*.heap.svg
  - cabal
  - lsp-types
  - all
  - all-binaries
  - profiled-cabal
  - profiled-lsp-types
  - profiled-all
  - profiled-all-binaries

[qrilka]

cabal bench ghcide seems to work, thanks @pepeiborra

[pepeiborra]

I was wrong, lsp-types is a valid rule and it works fine for me with cabal bench ghcide --benchmark-option="lsp-types" so I suspect you might run into further problems with cabal bench ghcide.

[qrilka]

It seems like the problem was about some files remaining from previous runs, after some cleanup lsp-types seems to work fine.