Skip to content

Remove coverage prep stage as this corrupts the coverage report#792

Merged
h5law merged 2 commits intomainfrom
codecov-uploader
May 30, 2023
Merged

Remove coverage prep stage as this corrupts the coverage report#792
h5law merged 2 commits intomainfrom
codecov-uploader

Conversation

@h5law
Copy link
Copy Markdown
Contributor

@h5law h5law commented May 28, 2023

Description

In the prepare code coverage report workflow job this actually corrupts the coverage report being uploaded to codecov resulting in a no usable upload error. This command (from my understanding) makes the coverage report readable for humans.

Issue

Fixes N/A

Type of change

Please mark the relevant option(s):

  • New feature, functionality or library
  • Bug fix
  • Code health or cleanup
  • Major breaking change
  • Documentation
  • Other

List of changes

  • Remove code coverage preparation step in workflow
  • Explicitly state the coverage file to be uploaded to codecov

Testing

  • make develop_test; if any code changes were made
  • make test_e2e on k8s LocalNet; if any code changes were made
  • e2e-devnet-test passes tests on DevNet; if any code was changed
  • Docker Compose LocalNet; if any major functionality was changed or introduced
  • k8s LocalNet; if any infrastructure or configuration changes were made

Required Checklist

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added, or updated, godoc format comments on touched members (see: tip.golang.org/doc/comment)
  • I have tested my changes using the available tooling
  • I have updated the corresponding CHANGELOG

If Applicable Checklist

  • I have updated the corresponding README(s); local and/or global
  • I have added tests that prove my fix is effective or that my feature works
  • I have added, or updated, mermaid.js diagrams in the corresponding README(s)
  • I have added, or updated, documentation and mermaid.js diagrams in shared/docs/* if I updated shared/*README(s)

@h5law h5law added the bug Something isn't working - expected behaviour is incorrect label May 28, 2023
@h5law h5law requested a review from Olshansk May 28, 2023 10:41
@h5law h5law self-assigned this May 28, 2023
@reviewpad reviewpad bot added small Pull request is small waiting-for-review labels May 28, 2023
@h5law h5law requested a review from okdas May 28, 2023 10:42
@codecov
Copy link
Copy Markdown

codecov bot commented May 28, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (95cf73d) 30.63% compared to head (2699e39) 30.63%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #792   +/-   ##
=======================================
  Coverage   30.63%   30.63%           
=======================================
  Files         102      102           
  Lines        8686     8686           
=======================================
  Hits         2661     2661           
  Misses       5699     5699           
  Partials      326      326           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

Copy link
Copy Markdown
Collaborator

@Olshansk Olshansk left a comment

Choose a reason for hiding this comment

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

Clicked through the codecov in your PR versus some of the others and can tell that it works.

Thanks for solving this proactively @h5law! 🚀

@h5law h5law merged commit 5d1944c into main May 30, 2023
@h5law h5law deleted the codecov-uploader branch May 30, 2023 21:51
bryanchriswhite added a commit that referenced this pull request May 31, 2023
* pokt/main:
  [P2P] refactor: message handling (#763)
  Remove coverage prep stage as this corrupts the coverage report (#792)
  [Utility] E2E Feature Path Template (#734)
Olshansk pushed a commit that referenced this pull request Jun 1, 2023
## Description

In the prepare code coverage report workflow job this actually corrupts
the coverage report being uploaded to codecov resulting in a no usable
upload error. This command (from my understanding) makes the coverage
report readable for humans.

## Issue

Fixes N/A

## Type of change

Please mark the relevant option(s):

- [ ] New feature, functionality or library
- [x] Bug fix
- [ ] Code health or cleanup
- [ ] Major breaking change
- [ ] Documentation
- [ ] Other <!-- add details here if it a different type of change -->

## List of changes

- Remove code coverage preparation step in workflow
- Explicitly state the coverage file to be uploaded to codecov

## Testing

- [ ] `make develop_test`; if any code changes were made
- [ ] `make test_e2e` on [k8s
LocalNet](https://github.com/pokt-network/pocket/blob/main/build/localnet/README.md);
if any code changes were made
- [ ] `e2e-devnet-test` passes tests on
[DevNet](https://pocketnetwork.notion.site/How-to-DevNet-ff1598f27efe44c09f34e2aa0051f0dd);
if any code was changed
- [ ] [Docker Compose
LocalNet](https://github.com/pokt-network/pocket/blob/main/docs/development/README.md);
if any major functionality was changed or introduced
- [ ] [k8s
LocalNet](https://github.com/pokt-network/pocket/blob/main/build/localnet/README.md);
if any infrastructure or configuration changes were made

## Required Checklist

- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have added, or updated, [`godoc` format
comments](https://go.dev/blog/godoc) on touched members (see:
[tip.golang.org/doc/comment](https://tip.golang.org/doc/comment))
- [ ] I have tested my changes using the available tooling
- [ ] I have updated the corresponding CHANGELOG

### If Applicable Checklist

- [ ] I have updated the corresponding README(s); local and/or global
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] I have added, or updated,
[mermaid.js](https://mermaid-js.github.io) diagrams in the corresponding
README(s)
- [ ] I have added, or updated, documentation and
[mermaid.js](https://mermaid-js.github.io) diagrams in `shared/docs/*`
if I updated `shared/*`README(s)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working - expected behaviour is incorrect small Pull request is small waiting-for-review

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants