You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 2, 2021. It is now read-only.
* Add github test action
* Disable unreliable test
Does not work reliably on all platforms.
Reenable when #861 lands
* Add hlint and -Werror
* Explicit timeout
6h is the default and also the maximum:
https://docs.github.com/en/free-pro-team@latest/actions/reference/usage-limits-billing-and-administration
* Experiment tests to use Cabal instead of Stack
* Fix an unreliable test
* Trim down matrix
* Add ghc-lib to the test matrix
* Address broken hie-compat ghc-lib build
* Drop stack descriptor family
We keep two stack descriptors:
- One for Nightly
- One for Windows (stuck in GHC 8.10.1)
To ensure that `stack test` doesn't break, we keep running the stack tests in CI
* Update README to point end users to HLS
* Drop support for `stack test`
Copy file name to clipboardExpand all lines: README.md
+11-8Lines changed: 11 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,6 +46,10 @@ a simple reproduction of the bug.
46
46
47
47
### Install `ghcide`
48
48
49
+
[We recommend](https://neilmitchell.blogspot.com/2020/09/dont-use-ghcide-anymore-directly.html) installing and using the Haskell extension in VS Code, or the prebuilt binaries provided by https://github.com/haskell/haskell-language-server
50
+
51
+
If you still wish to install `ghcide` direcly, the instructions below might prove useful *but you are on your own*.
52
+
49
53
#### With Nix
50
54
51
55
Note that you need to compile `ghcide` with the same `ghc` as the project you are working on.
@@ -317,13 +321,15 @@ args = ["--lsp"]
317
321
318
322
## Hacking on ghcide
319
323
320
-
To build and work on `ghcide` itself, you can use Stack or cabal, e.g.,
321
-
running `stack test` will execute the test suite.
324
+
To build and work on `ghcide` itself, you should use cabal, e.g.,
325
+
running `cabal test` will execute the test suite. You can use `stack test` too, but
326
+
note that some tests will fail, and none of the maintainers are currently using `stack`.
327
+
322
328
If you are using Windows, you should disable the `auto.crlf` setting and configure your editor to use LF line endings, directly or making it use the existing `.editor-config`.
323
329
324
330
If you are chasing down test failures, you can use the tasty-rerun feature by running tests as
325
331
326
-
stack --stack-yaml=stack84.yaml test --test-arguments "--rerun"
332
+
cabal test --test-options"--rerun"
327
333
328
334
This writes a log file called `.tasty-rerun-log` of the failures, and only runs those.
329
335
See the [tasty-rerun](https://hackage.haskell.org/package/tasty-rerun-1.1.17/docs/Test-Tasty-Ingredients-Rerun.html) documentation for other options.
@@ -332,12 +338,9 @@ If you are touching performance sensitive code, take the time to run a different
332
338
benchmark between HEAD and master using the benchHist script. This assumes that
333
339
"master" points to the upstream master.
334
340
335
-
Run the benchmarks with `stack`:
336
-
337
-
export STACK_YAML=...
338
-
stack bench
341
+
Run the benchmarks with `cabal bench`.
339
342
340
-
It should take around 15 minutes and the results will be stored in the `bench-hist` folder. To interpret the results, see the comments in the `bench/hist/Main.hs` module.
343
+
It should take around 15 minutes and the results will be stored in the `bench-results` folder. To interpret the results, see the comments in the `bench/hist/Main.hs` module.
0 commit comments