the linters are killing me slowly

[Matthew Pickering]

I think we could run the linters in the same step as the rest of the
builds. As long as  the hadrian-ghci job runs as the initial step to
weed out any obviously bad commits.

On Wed, Feb 9, 2022 at 7:15 PM Richard Eisenberg <lists at richarde.dev> wrote:
>
> Hi devs,
>
> Can we please, please not have the linters stop more useful output during CI? Over the past few months, I've lost several days of productivity due to the current design. Why several days? Because I typically end up with only 1.5-2 hours for GHC work in a day, and when I have to spend half of that recreating test results (which, sometimes, don't work, especially if I use Hadrian, as recommended), I often decide to prioritize other tasks that I have a more reasonable chance of actually finishing.
>
> It was floated some time ago that "Draft" MRs could skip linters. But I actually have a non-Draft MR now, and it failed the new Notes linter. (Why, actually, is that even a separate pass? I thought there was a test case for that, which I'm thrilled with.)
>
> It just feels to me that the current workflow is optimized for those of us who work on GHC close to 100% of the time. This is not the way to get new contributors.
>
> Frustrated,
> Richard
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs