Skip to content

v2.1.x Chore - Consider using more robust error handling when combining coverage files. #363

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
reactive-firewall opened this issue Apr 15, 2025 · 0 comments
Labels
Bash Lang Changes to the BASH scripts Chore Miscellaneous chores to maintain the project Linter Any linter tool or setting file enhancements

Comments

@reactive-firewall
Copy link
Owner

reactive-firewall commented Apr 15, 2025

Consider using more robust error handling when combining coverage files. The current approach might miss some edge cases where .coverage.* files don't exist.

Originally posted by @codecov-ai[bot] in #361 (comment)

goal This is just a chore for when next refactoring the tests/check_integration_coverage script.

@reactive-firewall reactive-firewall added Linter Any linter tool or setting file enhancements Bash Lang Changes to the BASH scripts labels Apr 15, 2025
@reactive-firewall reactive-firewall changed the title Chore - Consider using more robust error handling when combining coverage files. v2.1.x Chore - Consider using more robust error handling when combining coverage files. Apr 17, 2025
@reactive-firewall reactive-firewall added the Chore Miscellaneous chores to maintain the project label Jun 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bash Lang Changes to the BASH scripts Chore Miscellaneous chores to maintain the project Linter Any linter tool or setting file enhancements
Projects
Status: To do
Development

No branches or pull requests

1 participant