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

build(coverage): fix carry-forward coverage #12306

Merged
merged 2 commits into from
Jan 9, 2025

Conversation

chakru-r
Copy link
Collaborator

@chakru-r chakru-r commented Jan 9, 2025

Code coverage carry-forward is tied to flags (used to represent modules/subprojects) and code coverage for a flag can be carried forward if ci optimizations skips a module build. So created a module flag for each group of projects that the ci builds together. This roughly corresponds to the groups defined in ci-optimization action.

Checklist

  • The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
  • Links to related issues (if applicable)
  • Tests for the changes have been added/updated (if applicable)
  • Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
  • For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@github-actions github-actions bot added the devops PR or Issue related to DataHub backend & deployment label Jan 9, 2025
@chakru-r chakru-r force-pushed the codecov-carry-forward branch from e1fcb8e to 89d2bd2 Compare January 9, 2025 12:12
Copy link

codecov bot commented Jan 9, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 42b2cd3...9b567d1. Read the comment docs.

@chakru-r chakru-r force-pushed the codecov-carry-forward branch from 89d2bd2 to 08efaa9 Compare January 9, 2025 12:38
@chakru-r chakru-r marked this pull request as ready for review January 9, 2025 13:19
Code coverage carry-forward is tied to flags (used to present
modules/subprojects) and code coverage for a flag can be carried forward if
ci optimizations skips a module build. So created a module `flag` for each
group of projects that the ci builds together. This roughly corresponds to
the groups defined in ci-optimization action.
@chakru-r chakru-r force-pushed the codecov-carry-forward branch from 08efaa9 to 9b567d1 Compare January 9, 2025 13:20
@datahub-cyborg datahub-cyborg bot added the needs-review Label for PRs that need review from a maintainer. label Jan 9, 2025
@datahub-cyborg datahub-cyborg bot added pending-submitter-merge and removed needs-review Label for PRs that need review from a maintainer. labels Jan 9, 2025
@chakru-r chakru-r merged commit d3ac112 into datahub-project:master Jan 9, 2025
210 of 237 checks passed
llance pushed a commit to llance/datahub that referenced this pull request Jan 13, 2025
llance pushed a commit to llance/datahub that referenced this pull request Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops PR or Issue related to DataHub backend & deployment pending-submitter-merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants