rubocop on Windows: 22 files inspected, 22 offenses detected

[jgfoster]

It complains about CR characters being present but the test does not fail. This raises a couple questions:

• If we have an automated test that reports a problem but the framework doesn't tell us about it, then something is broken.
• Why do 22 files have CR on Windows?

[ianfixes]

I wonder if this has anything to do with the text=auto setting that we had applied earlier in the git config

[jgfoster]

That's something that I'm investigating as part of #314 (and once we merge that we can revisit this). But even if it does explain the second issue it doesn't address the first issue of failing tests that aren't being reported by the CI system (see here for the problem).

[jgfoster]

When rubocop and rspec are combined in one job, a failure in rubocop will be ignored. But if they are separated then the error will be caught. Compare the Linux workflow with the Windows workflow.

[ianfixes]

I think they should definitely be separated. Also, I should set something up for presenting the rubocop failures as line-level annotations in the diff, not just a pass/fail.

Note to self: https://github.com/marketplace/actions/rubocop-annotate-action