You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Currently, the updated coverage reports aren't being pushed if the coverage threshold is not satisfied (Results job fails) even if manually approved. This is shown in PR #209 which will affect coverage comparisons for upcoming PRs.
High chances of new PRs failing because comparing to old coverage values/reports.
Expected behavior
Even if comparison is below threshold, update coverage reports/values for current PR. This will involve removing success check for Update job because currently the job is completely skipped if this occurs and doesn't update anything.
Screenshots
The text was updated successfully, but these errors were encountered:
cwlacewe
added
Bug
Indicates unexpected or undesired behaviors
Workflow
Improvements specific to development workflow (i.e. CI changes, unit testing, etc.)
labels
Sep 10, 2024
* Run Update job even if comparison fails in order to update coverage reports (accounts for manual approvals)
* Automated updates: Format and/or coverage
* Modify to always run update job
---------
Co-authored-by: sys_vdms <[email protected]>
Describe the bug
Currently, the updated coverage reports aren't being pushed if the coverage threshold is not satisfied (Results job fails) even if manually approved. This is shown in PR #209 which will affect coverage comparisons for upcoming PRs.
High chances of new PRs failing because comparing to old coverage values/reports.
Expected behavior
Even if comparison is below threshold, update coverage reports/values for current PR. This will involve removing
success
check for Update job because currently the job is completely skipped if this occurs and doesn't update anything.Screenshots
The text was updated successfully, but these errors were encountered: