Skip to content

Fix compression policy error message. #8008

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

gayyappan
Copy link
Contributor

The number of successes was calculated incorrectly.

Copy link

codecov bot commented Apr 24, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.19%. Comparing base (59f50f2) to head (053a775).
Report is 921 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #8008      +/-   ##
==========================================
+ Coverage   80.06%   82.19%   +2.13%     
==========================================
  Files         190      252      +62     
  Lines       37181    46498    +9317     
  Branches     9450    11688    +2238     
==========================================
+ Hits        29770    38221    +8451     
- Misses       2997     3639     +642     
- Partials     4414     4638     +224     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@fabriziomello
Copy link
Member

@gayyappan I'm thinking if we should provide a way to fix the wrong error messages on _timescaledb_interna.bgw_job_stat_history table. WDYT?

@fabriziomello
Copy link
Member

Another thing that bother me is that we don't have a proper regression test for it, or do we have?

@fabriziomello fabriziomello force-pushed the try branch 4 times, most recently from f6d3d74 to 6053417 Compare April 24, 2025 21:10
@fabriziomello fabriziomello self-assigned this Apr 24, 2025
@fabriziomello fabriziomello force-pushed the try branch 3 times, most recently from 6e3415d to 385d6fe Compare April 26, 2025 18:23
Co-authored-by: Fabrízio de Royes Mello <[email protected]>
@fabriziomello
Copy link
Member

Another thing that bother me is that we don't have a proper regression test for it, or do we have?

Added regression tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants