Skip to content
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

Update code coverage orbs #2206

Merged
merged 3 commits into from Sep 28, 2023
Merged

Update code coverage orbs #2206

merged 3 commits into from Sep 28, 2023

Conversation

bouweandela
Copy link
Member

@bouweandela bouweandela commented Sep 26, 2023

Description

Update the CircleCI orbs for reporting code coverage to a more recent version.


Before you get started

Checklist

It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the πŸ›  Technical or πŸ§ͺ Scientific review.


To help with the number pull requests:

@codecov
Copy link

codecov bot commented Sep 26, 2023

Codecov Report

Merging #2206 (ccce94c) into main (dcc9645) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2206   +/-   ##
=======================================
  Coverage   93.31%   93.31%           
=======================================
  Files         238      238           
  Lines       13028    13028           
=======================================
  Hits        12157    12157           
  Misses        871      871           

@bouweandela bouweandela marked this pull request as ready for review September 26, 2023 20:12
@bouweandela bouweandela added this to the v2.10.0 milestone Sep 26, 2023
@@ -124,6 +124,9 @@ jobs:
- /root/.cache/pip
- .mypy_cache
- .pytest_cache
- run:
name: Install gpg (required by codecov orb)
command: apt update && apt install -y gpg
- codecov/upload:
when: always
file: 'test-reports/coverage.xml'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what's the report.xml created above used for then?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's used to generate the test summary page: https://app.circleci.com/pipelines/github/ESMValGroup/ESMValCore/9756/workflows/2169fe35-d00d-448d-826f-eeaa47109d51/jobs/42339/tests

That looks quite boring for this pr, but if there are some failing tests it gives you a nice quick overview without having to scroll through lots of terminal output.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

aha! Nice one then, thanks

@valeriupredoi
Copy link
Contributor

not really liking this new stuff though - it says there are 11 scripts with some indirect chamges to coverage but when I try clicking on one it tells me some error occured (that might be if Codecov server is down) - but those scripts used to be listed in the table in the codecov comment on the PR page - will those be gone now and only visible at the Codecov page? See this for one of those scripts I emntion

@bouweandela
Copy link
Member Author

It looks like the issue solved itself when the coverage for the latest commit got uploaded.

Copy link
Contributor

@valeriupredoi valeriupredoi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK progress I guess but I liked that table with up/down coverage per file, in the bot's comment

@valeriupredoi
Copy link
Contributor

It looks like the issue solved itself when the coverage for the latest commit got uploaded.

still getting the error, but it may be that my Firefox is that old that it's not even called Firefox, and some fansy new Javascript is not found

@bouweandela
Copy link
Member Author

bouweandela commented Sep 28, 2023

OK progress I guess but I liked that table with up/down coverage per file, in the bot's comment

The table is only shown when there are files with changed coverage in the PR, that's why you don't see it here.

@valeriupredoi
Copy link
Contributor

OK progress I guess but I liked that table with up/down coverage per file, in the bot's comment

The table is only shown when there are files with changed coverage in the PR, that's why you don't see it here.

I suspected that but I was a bit taken aback by those "files with indirect changes" links I saw earlier - at any rate, am merging this, we spent too much time discussing it already 😁

@valeriupredoi valeriupredoi merged commit e296491 into main Sep 28, 2023
4 checks passed
@valeriupredoi valeriupredoi deleted the update-code-coverage-orbs branch September 28, 2023 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants