2 Configuration is affected by the following files:
4 Resolving dependencies...
5 Warning: Some RTS options were found standalone, which affect cabal and not the binary. Please note that +RTS inside the --benchmark-options argument suffices if your goal is to affect the benchmarked binary. For example, use "cabal test --benchmark-options='+RTS -N'" to pass the '-N' RTS option to your binary.
6 Build profile: -w ghc-<GHCVER> -O1
7 In order, the following will be built:
8 - WarningRTS-1.0 (bench:foo) (first run)
9 Configuring benchmark 'foo' for WarningRTS-1.0...
10 Preprocessing benchmark 'foo' for WarningRTS-1.0...
11 Building benchmark 'foo' for WarningRTS-1.0...
12 Running 1 benchmarks...
13 Benchmark foo: RUNNING...
16 Configuration is affected by the following files:
18 Warning: Some RTS options were found standalone, which affect cabal and not the binary. Please note that +RTS inside the --benchmark-options argument suffices if your goal is to affect the benchmarked binary. For example, use "cabal test --benchmark-options='+RTS -N'" to pass the '-N' RTS option to your binary.
19 Build profile: -w ghc-<GHCVER> -O1
20 In order, the following will be built:
21 - WarningRTS-1.0 (bench:foo) (first run)
22 Preprocessing benchmark 'foo' for WarningRTS-1.0...
23 Building benchmark 'foo' for WarningRTS-1.0...
24 Running 1 benchmarks...
25 Benchmark foo: RUNNING...
28 Configuration is affected by the following files:
30 Build profile: -w ghc-<GHCVER> -O1
31 In order, the following will be built:
32 - WarningRTS-1.0 (bench:foo) (first run)
33 Preprocessing benchmark 'foo' for WarningRTS-1.0...
34 Building benchmark 'foo' for WarningRTS-1.0...
35 Running 1 benchmarks...
36 Benchmark foo: RUNNING...