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

coveralls github action stopped working with pytest-cov #126

Open
altaurog opened this issue May 7, 2024 · 4 comments
Open

coveralls github action stopped working with pytest-cov #126

altaurog opened this issue May 7, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@altaurog
Copy link

altaurog commented May 7, 2024

What was wrong?

coveralls reporter was working with pytest-cov out of the box, but seems to have stopped

I tried pinning coverage and pytest-cov to last working version, but it still fails.

Logs

https://github.com/altaurog/pgcopy/actions/runs/8981185693/job/24666223762#step:6:69

⠀⠀⠀⠀⠀⠀⣿
⠀⠀⠀⠀⠀⣼⣿⣧⠀⠀⠀⠀⠀⠀⠀ ⣠⣶⣾⣿⡇⢀⣴⣾⣿⣷⣆ ⣿⣿⠀⣰⣿⡟⢸⣿⣿⣿⡇ ⣿⣿⣿⣷⣦⠀⠀⢠⣿⣿⣿⠀⠀⣿⣿⠁⠀⣼⣿⡇⠀⢀⣴⣾⣿⡷
⠶⣶⣶⣶⣾⣿⣿⣿⣷⣶⣶⣶⠶  ⣸⣿⡟ ⠀⢠⣿⣿⠃⠈⣿⣿⠀⣿⣿⢠⣿⡿⠀⣿⣿⣧⣤⠀⢸⣿⡇⣠⣿⡿⠀⢠⣿⡟⣿⣿⠀⢸⣿⡿⠀⠀⣿⣿⠃⠀⢸⣿⣧⣄
⠀⠀⠙⢻⣿⣿⣿⣿⣿⡟⠋⠁⠀⠀ ⣿⣿⡇⠀ ⢸⣿⣿⠀⣸⣿⡟⠀⣿⣿⣾⡿⠁ ⣿⣿⠛⠛⠀⣿⣿⢿⣿⣏⠀⢀⣿⣿⣁⣿⣿⠀⣾⣿⡇⠀⢸⣿⡿⠀⠀⡀⠙⣿⣿⡆
⠀⠀⢠⣿⣿⣿⠿⣿⣿⣿⡄⠀⠀⠀ ⠙⢿⣿⣿⠇⠈⠿⣿⣿⡿⠋⠀⠀⢿⣿⡿⠁⠀⢸⣿⣿⣿⡇⢸⣿⣿⠀⣿⣿⣄⣾⣿⠛⠛⣿⣿⢠⣿⣿⣿ ⣼⣿⣿⣿ ⣿⣿⡿⠋⠀
⠀⢀⣾⠟⠋⠀⠀⠀⠙⠻⣷⡀⠀⠀
 
  v0.6.10

🔍 Detected coverage file: .coverage
⚠️ Coverage reporter does not yet know how to process this file: .coverage
🚨 Nothing to report
Error: Process completed with exit code 1.

It worked with v0.6.6 in this run:

https://github.com/altaurog/pgcopy/actions/runs/8602391600/job/23571855578#step:6:71

@altaurog altaurog added the bug Something isn't working label May 7, 2024
@altaurog
Copy link
Author

altaurog commented May 7, 2024

it works if I configure lcov output from pytest-cov

@altaurog
Copy link
Author

altaurog commented May 7, 2024

I see this was reported already: coverallsapp/github-action#205
apparently relevant: #116, #120, #122
apologies if this is just a duplicate

@altaurog
Copy link
Author

altaurog commented May 7, 2024

Incidentally, processing lcov output also gave me the correct results, whereas with the default .coverage output I observed a discrepancy in the reported coverage which seemed to stem from improper parsing of the python files. (Perhaps that should have been reported here? There are so many different issue trackers, I am not sure what to report where.)

@littleforest
Copy link
Collaborator

@altaurog we just released version 0.6.11 which fixed some issues when users were specifying a coverage format. Could you please test with the latest version and let us know if you are still running into issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants