Might want to also remove thefail_ci_if_error parameter, so that the codecov step itself returns an error status and is visibly marked as failing, even if it doesn't cause the rest of the job to fail.

@dwahler It defaults tofalse, so we'd need to set it totrue, actually. Also, issue seems to be resolved now (at least for ubuntu and macos runners so-far), but I don't think merging this would be a bad idea even then, thoughts?

@dwahler actually, I'm not brave enough to setfail_ci_if_error: true since I don't know by what mechanism it's going to fail the action. As-such, I just cleaned it up a bit and added a comment explaining it.