Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[skip circleci] Rename hlint test data files and add regression tests #2321

Merged
merged 21 commits into from
Nov 10, 2021

Conversation

jneira
Copy link
Member

@jneira jneira commented Nov 1, 2021

@jneira jneira changed the title Rename test data files [skip circleci] Rename test data files Nov 1, 2021
@jneira jneira changed the title [skip circleci] Rename test data files [skip circleci] Rename hlint test data files and add regression tests Nov 1, 2021
@jneira jneira marked this pull request as draft November 1, 2021 19:21
@jneira jneira marked this pull request as ready for review November 6, 2021 10:41
@jneira
Copy link
Member Author

jneira commented Nov 8, 2021

Tests are green after the usual reruns, so I think it could be reviewed although most changes are naming related

Copy link
Collaborator

@michaelpj michaelpj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct waitForProgressDone hls-test-utils implementation: it was a exact duplicate of waitForAllProgressDone so it is replaced with the definition from the same function in the ghcide test suite

Can we share this? Perhaps we need to upstream some more test helpers into lsp-test?

@@ -285,3 +316,9 @@ hlintConfigWithFlags flags =
where
unObject (Object obj) = obj
unObject _ = undefined

knownBrokenForHlintOnGhcLib :: String -> TestTree -> TestTree
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not immediately obvious to me what these mean or why it's these versions. Haddock?

Copy link
Member Author

@jneira jneira Nov 10, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm it is a somewhat long history, will try to add a concise comment although the entire thing should be explained in the plugin README or something (TBD)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if i explained it clearly 🤔

@jneira jneira added the merge me Label to trigger pull request merge label Nov 10, 2021
@mergify mergify bot merged commit 7011d5e into haskell:master Nov 10, 2021
@jneira
Copy link
Member Author

jneira commented Nov 10, 2021

Err why mergify merged the pr without waiting for required checks?, argh

@jneira
Copy link
Member Author

jneira commented Nov 10, 2021

I think the post_job's are not shown until they have started, so if test postjob has not started but benchmark or nix one have ended succesfully, you can merge the pr, will try to fix giving them unique names

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merge me Label to trigger pull request merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants