Andreas Abel

This PR has been rotting here for more than 7 years. Is there still interest?

In general, an executable can be used in a testsuite by `cabal test` if it is declared as _build dependency_. For an example, testing "myself" (`agda2lagda`) using `goldplate`, see: https://github.com/andreasabel/agda2lagda/blob/93d317c87bddf973e3fa6abd5bf24dcfa9a797f0/agda2lagda.cabal#L104-L115...

> ``` > $ runghc Setup.hs configure --enable-tests -v3 > ``` I have not tested this since I am always using the `cabal` command. Is there an issue on this...

Me too. See https://github.com/agda/agda/runs/4200138734?check_suite_focus=true#step:11:2537 In my case it is `haskeline-0.8.2`: https://github.com/agda/agda/runs/4200138734?check_suite_focus=true#step:11:2749

Here are some build failures with GHC 9.2: ``` $ cabal build --constraint='Win32 < 2.12' --constraint='time

`c_WaitForSingleObject` was introduced in b2b86de908e2478f2c24cf67a31ca84f1e342352 (@RyanGlScott 's Christmas present to haskeline of 2015) which has been released in 0.7.2.3 (see https://github.com/judah/haskeline/compare/0.7.2.2...0.7.2.3). Thus, I speculate that all versions >= 0.7.2.3 do...

Travis is gone, so I suppose this PR can be closed. A CI on github actions can be auto-generated with `Haskell-CI`.

@bgamari: This PR can be closed.

I suppose this PR is stale now and can be closed.

Ping @judah