Our coverage checking config with coveralls.io is broken

[john-science]

On Friday, our coveralls.io CI, which displays and reports our code coverage, broke.

The only clue as to why it broke is it is complaining we need a auth token in our GH Actions env.

Well, fine. But I don't have permissions to log into the ARMI coveralls.io account and find such a token. And the last 15 months we certainly haven't used one. So. Unless @youngmit or @ntouran have access to that coveralls.io account, that is dead in the water. BUT... honestly, coveralls has always been flaky (see this ticket.

Our build will be broke until we ditch coveralls.io.

[ntouran]

Yeah I'm like 99% sure I have that login. We can configure the auth there as needed, shouldn't be too hard. maybe our original token expired.

[john-science]

Holler when you find it!

[ntouran]

Ok I have it. The error you linked above says:

coveralls.exception.CoverallsException: Not on TravisCI. You have to provide either repo_token in .coveralls.yml or set the COVERALLS_REPO_TOKEN env var.

So I guess we can just set the COVERALLS_REPO_TOKEN to the token I see in our GH Actions config somewhere, eh?

[ntouran]

I am looking for more explicit docs explaining this though. Right now when you go to https://docs.coveralls.io/ and click on the github actions thing it takes you to their nicely-packaged coveralls GH action which I don't think we're using. We only mention coveralls in the tox.ini file. Maybe we should adjust our config to be up-to-date with the services docs?

[ntouran]

Anyway, my PR did ok but not all the way. commenting in there as we work though it.