Simon Hengel

This is the error I'm getting with GHC 9.2.1: ``` linking dist/build/System/Clock_hsc_make.o failed (exit code 1) rsp file was: "dist/build/System/hsc2hscall441822-2.rsp" command was: /usr/bin/gcc dist/build/System/Clock_hsc_make.o dist/build/System/Clock_hsc_utils.o -o dist/build/System/Clock_hsc_make -fuse-ld=gold -fuse-ld=gold -L/home/sol/.install/haskell/ghc-9.2.1/lib/ghc-9.2.1/base-4.16.0.0...

> > Both of these events are reasonably rare, so I hope this is the right thing to do. > > Is `getMonotonicTime` only used to measure the speed of...

It turns out that we can use `GHC.Clock.getMonotonicTime` with recent versions of GHC.

Before discussing this in more detail, are you running your tests concurrently? If yes, have you tried to limit concurrency**? ** Pass `--jobs=4` to your test driver (as an alternative,...

> I dug around in the code for a bit last night but was unable to figure out precisely what is determining the duration, or if there's anything done to...

> We want to assert that a test does not take longer than 60s. Sometimes just acquiring a database connection would take that long in CI Did you try `--jobs=4`...

> However, our `after` action involves deleting the database tables and getting back to a fresh start, and that _is_ being reflected in the test duration Ok, so from what...

@hdgarrood I agree. It won’t work for user journey tests and some acceptance tests.

> Ideally, the `Duration` for a test would only be on the actual test example itself, not all the stuff `before` or `after` it. Revisiting this issue, I understand that...

@blackheaven sorry for the late reply. Some thoughts (in no particular order): - The underlying problem is that the diff implementation is slow, much slower than GNU diff. Doing things...