coverallsapp / coverage-reporter

Self-contained, universal coverage uploader binary. Under development.
https://coveralls.io
MIT License
45 stars 14 forks source link

coveralls github action stopped working with pytest-cov #126

Open altaurog opened 2 months ago

altaurog commented 2 months ago

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 commented 2 months ago

it works if I configure lcov output from pytest-cov

altaurog commented 2 months ago

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

altaurog commented 2 months ago

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 commented 1 month ago

@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.