-
-
Notifications
You must be signed in to change notification settings - Fork 388
Trace diagnostics #2333
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
Trace diagnostics #2333
Conversation
We already disable this in ghcide tests It introduces noise (traces are harder to read), and can potentially break tests too (e.g. eval plugin)
could we keep some tests with the option enabled? it is the default for now and maybe would be good to keep it covered in some way |
There are tests that exercise this option in the ghcide test suite already. I'll have a look at the splice plugin test failures, maybe that test suite depends on this option being enabled for some reason |
bae0528
to
6264f5a
Compare
@jneira this is ready to merge now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Include rule diagnostics in traces for diagnosing diagnostic issues
Also disable checkProject in HLS test suite.
We already disable this in ghcide tests, since it introduces noise (traces are harder to read), and can potentially break tests too (e.g. eval plugin)