-
Notifications
You must be signed in to change notification settings - Fork 715
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
CI settings prevent updates to older gaias #1449
Comments
yep. this one, dated a month ago, detailed the issues with all the pr's |
Hey @faddat do have suggestions for alternative codecov tooling? |
Just had a call with @okwme -- so, we found that the linter was missing this line: However, the main branch contains linting issues. They're not being caught because of the diff. They are grandfathered-in. We saw this with: |
Linting errors should all be fixed at this point in main. |
Update:
|
Closing as codecov was updated to Sonarcloud. If the problem persists, we'll reopen. |
Summary of Bug
Version
all
Steps to Reproduce
Update older versions of gaia, or in the case of the codecov issue, do anything at all
https://github.com/cosmos/gaia/runs/6164055056?check_suite_focus=true#step:8:30
Suggested solutions
#1448
note
due to the fact that there seems an issue with the cosmos codecov api key generally or with the whole service, any PR's that have cone in recently will need their ci jobs re-run
this has hit tm-db as well:
https://github.com/tendermint/tm-db/runs/6163210118?check_suite_focus=true
2nd note:
it hurts more than the linters
https://github.com/faddat/gaia/blob/84de16ef50b0dad6ec164b99610a80bf16d9ec01/.github/workflows/sims.yml#L125
ci jobs are free, why are we trying to conserve them?
For Admin Use
The text was updated successfully, but these errors were encountered: