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

Unable to upload report using coverage-reporter v0.6.8 #119

Closed
ogenstad opened this issue Apr 9, 2024 · 12 comments
Closed

Unable to upload report using coverage-reporter v0.6.8 #119

ogenstad opened this issue Apr 9, 2024 · 12 comments
Labels
bug Something isn't working

Comments

@ogenstad
Copy link

ogenstad commented Apr 9, 2024

What was wrong?

I'm not able to upload the report using the 0.6.8 version that was just released.

Logs

Run coverallsapp/github-action@v2
Run mkdir -p ~/bin/
coveralls-linux.tar.gz: OK
Run coveralls report        
 
⠀⠀⠀⠀⠀⠀⣿
⠀⠀⠀⠀⠀⣼⣿⣧⠀⠀⠀⠀⠀⠀⠀ ⣠⣶⣾⣿⡇⢀⣴⣾⣿⣷⣆ ⣿⣿⠀⣰⣿⡟⢸⣿⣿⣿⡇ ⣿⣿⣿⣷⣦⠀⠀⢠⣿⣿⣿⠀⠀⣿⣿⠁⠀⣼⣿⡇⠀⢀⣴⣾⣿⡷
⠶⣶⣶⣶⣾⣿⣿⣿⣷⣶⣶⣶⠶  ⣸⣿⡟ ⠀⢠⣿⣿⠃⠈⣿⣿⠀⣿⣿⢠⣿⡿⠀⣿⣿⣧⣤⠀⢸⣿⡇⣠⣿⡿⠀⢠⣿⡟⣿⣿⠀⢸⣿⡿⠀⠀⣿⣿⠃⠀⢸⣿⣧⣄
⠀⠀⠙⢻⣿⣿⣿⣿⣿⡟⠋⠁⠀⠀ ⣿⣿⡇⠀ ⢸⣿⣿⠀⣸⣿⡟⠀⣿⣿⣾⡿⠁ ⣿⣿⠛⠛⠀⣿⣿⢿⣿⣏⠀⢀⣿⣿⣁⣿⣿⠀⣾⣿⡇⠀⢸⣿⡿⠀⠀⡀⠙⣿⣿⡆
⠀⠀⢠⣿⣿⣿⠿⣿⣿⣿⡄⠀⠀⠀ ⠙⢿⣿⣿⠇⠈⠿⣿⣿⡿⠋⠀⠀⢿⣿⡿⠁⠀⢸⣿⣿⣿⡇⢸⣿⣿⠀⣿⣿⣄⣾⣿⠛⠛⣿⣿⢠⣿⣿⣿ ⣼⣿⣿⣿ ⣿⣿⡿⠋⠀
⠀⢀⣾⠟⠋⠀⠀⠀⠙⠻⣷⡀⠀⠀
 
  v0.6.8

🔍 Detected coverage file: coverage.xml
🔍 Detected coverage file: .coverage
#<CoverageReporter::CoveragepyParser::ParserError:--: 1: coverage: not found
>

As we're still waiting for coverallsapp/github-action#170 I don't know if I have any options now using the github-action.

Please let me know if I need to provide any additional information around this, or if I can do something on my end to fix it.

@ogenstad ogenstad added the bug Something isn't working label Apr 9, 2024
@pjhoberman
Copy link

We're seeing this as well with our circleci integration.

@matthieudesprez
Copy link

Same here using latest circleci orb coveralls/coveralls@2.2.1

@jacekbj
Copy link

jacekbj commented Apr 10, 2024

Isn't coverage now required indirectly?

ac469ac#diff-b07b49e9438f2f536ecc020f2c360f6afd54e56006bd7aa2b59cfff0a6338369R33

Tests don't fail because coverage is installed explicitly in ci.yml.

@pjhoberman
Copy link

Isn't coverage now required indirectly?

We have coverage in our requirements, and I just tested via shell to ensure coverage is present on the box and it is.

circleci@31e6e1eee119:~/project$ ./coveralls report --debug
 
⠀⠀⠀⠀⠀⠀⣿
⠀⠀⠀⠀⠀⣼⣿⣧⠀⠀⠀⠀⠀⠀⠀ ⣠⣶⣾⣿⡇⢀⣴⣾⣿⣷⣆ ⣿⣿⠀⣰⣿⡟⢸⣿⣿⣿⡇ ⣿⣿⣿⣷⣦⠀⠀⢠⣿⣿⣿⠀⠀⣿⣿⠁⠀⣼⣿⡇⠀⢀⣴⣾⣿⡷
⠶⣶⣶⣶⣾⣿⣿⣿⣷⣶⣶⣶⠶  ⣸⣿⡟ ⠀⢠⣿⣿⠃⠈⣿⣿⠀⣿⣿⢠⣿⡿⠀⣿⣿⣧⣤⠀⢸⣿⡇⣠⣿⡿⠀⢠⣿⡟⣿⣿⠀⢸⣿⡿⠀⠀⣿⣿⠃⠀⢸⣿⣧⣄
⠀⠀⠙⢻⣿⣿⣿⣿⣿⡟⠋⠁⠀⠀ ⣿⣿⡇⠀ ⢸⣿⣿⠀⣸⣿⡟⠀⣿⣿⣾⡿⠁ ⣿⣿⠛⠛⠀⣿⣿⢿⣿⣏⠀⢀⣿⣿⣁⣿⣿⠀⣾⣿⡇⠀⢸⣿⡿⠀⠀⡀⠙⣿⣿⡆
⠀⠀⢠⣿⣿⣿⠿⣿⣿⣿⡄⠀⠀⠀ ⠙⢿⣿⣿⠇⠈⠿⣿⣿⡿⠋⠀⠀⢿⣿⡿⠁⠀⢸⣿⣿⣿⡇⢸⣿⣿⠀⣿⣿⣄⣾⣿⠛⠛⣿⣿⢠⣿⣿⣿ ⣼⣿⣿⣿ ⣿⣿⡿⠋⠀
⠀⢀⣾⠟⠋⠀⠀⠀⠙⠻⣷⡀⠀⠀
 
  v0.6.8

🔍 Detected coverage file: .coverage
☝️ Detected coverage format: python - .coverage
⏱️ Report parsing: 00:00:00.052937362
Unhandled exception: --: 1: coverage: not found
 (CoverageReporter::CoveragepyParser::ParserError)
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
circleci@31e6e1eee119:~/project$ pip list
Package                           Version     Editable project location
--------------------------------- ----------- --------------------------
...
coverage                          7.4.4
...

@afinetooth
Copy link
Member

All,

Thanks for the reports. We're working on an update that we hope to release shortly. I'll come back with an update.

Thanks.

mike-burns added a commit that referenced this issue Apr 10, 2024
The new parser fails for many people on CI because it requires a
command-line tool that is proving tricky to guarantee installed and, if
installed, tricky to guarantee we can find it.

As a stopgap, revert that change and push that release out. The work in
the commit is good, but we need to focus more on ensuring access to the
command-line tool.

This reverts commit ac469ac. Closes #119
@mike-burns
Copy link
Contributor

I've reverted the coverage.py change that is leading to these errors, and cut release 0.6.9.

I'm closing this issue, but please comment here if it's still a problem.

@afinetooth
Copy link
Member

Thanks, @mike-burns. If anyone's still having issues let us know. If it's urgent, feel free to email me at support@coveralls.io.

@jan-janssen
Copy link

0.6.10 has the same bug:

Run coverallsapp/github-action@v2
Run mkdir -p ~/bin/
coveralls-linux.tar.gz: OK
Run coveralls report        
 
⠀⠀⠀⠀⠀⠀⣿
⠀⠀⠀⠀⠀⣼⣿⣧⠀⠀⠀⠀⠀⠀⠀ ⣠⣶⣾⣿⡇⢀⣴⣾⣿⣷⣆ ⣿⣿⠀⣰⣿⡟⢸⣿⣿⣿⡇ ⣿⣿⣿⣷⣦⠀⠀⢠⣿⣿⣿⠀⠀⣿⣿⠁⠀⣼⣿⡇⠀⢀⣴⣾⣿⡷
⠶⣶⣶⣶⣾⣿⣿⣿⣷⣶⣶⣶⠶  ⣸⣿⡟ ⠀⢠⣿⣿⠃⠈⣿⣿⠀⣿⣿⢠⣿⡿⠀⣿⣿⣧⣤⠀⢸⣿⡇⣠⣿⡿⠀⢠⣿⡟⣿⣿⠀⢸⣿⡿⠀⠀⣿⣿⠃⠀⢸⣿⣧⣄
⠀⠀⠙⢻⣿⣿⣿⣿⣿⡟⠋⠁⠀⠀ ⣿⣿⡇⠀ ⢸⣿⣿⠀⣸⣿⡟⠀⣿⣿⣾⡿⠁ ⣿⣿⠛⠛⠀⣿⣿⢿⣿⣏⠀⢀⣿⣿⣁⣿⣿⠀⣾⣿⡇⠀⢸⣿⡿⠀⠀⡀⠙⣿⣿⡆
⠀⠀⢠⣿⣿⣿⠿⣿⣿⣿⡄⠀⠀⠀ ⠙⢿⣿⣿⠇⠈⠿⣿⣿⡿⠋⠀⠀⢿⣿⡿⠁⠀⢸⣿⣿⣿⡇⢸⣿⣿⠀⣿⣿⣄⣾⣿⠛⠛⣿⣿⢠⣿⣿⣿ ⣼⣿⣿⣿ ⣿⣿⡿⠋⠀
⠀⢀⣾⠟⠋⠀⠀⠀⠙⠻⣷⡀⠀⠀
 
  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.

@ogenstad
Copy link
Author

I think that's something else 0.6.10 is working as expected for me:

Run coverallsapp/github-action@v2
Run mkdir -p ~/bin/
coveralls-linux.tar.gz: OK
Run coveralls report        
 
⠀⠀⠀⠀⠀⠀⣿
⠀⠀⠀⠀⠀⣼⣿⣧⠀⠀⠀⠀⠀⠀⠀ ⣠⣶⣾⣿⡇⢀⣴⣾⣿⣷⣆ ⣿⣿⠀⣰⣿⡟⢸⣿⣿⣿⡇ ⣿⣿⣿⣷⣦⠀⠀⢠⣿⣿⣿⠀⠀⣿⣿⠁⠀⣼⣿⡇⠀⢀⣴⣾⣿⡷
⠶⣶⣶⣶⣾⣿⣿⣿⣷⣶⣶⣶⠶  ⣸⣿⡟ ⠀⢠⣿⣿⠃⠈⣿⣿⠀⣿⣿⢠⣿⡿⠀⣿⣿⣧⣤⠀⢸⣿⡇⣠⣿⡿⠀⢠⣿⡟⣿⣿⠀⢸⣿⡿⠀⠀⣿⣿⠃⠀⢸⣿⣧⣄
⠀⠀⠙⢻⣿⣿⣿⣿⣿⡟⠋⠁⠀⠀ ⣿⣿⡇⠀ ⢸⣿⣿⠀⣸⣿⡟⠀⣿⣿⣾⡿⠁ ⣿⣿⠛⠛⠀⣿⣿⢿⣿⣏⠀⢀⣿⣿⣁⣿⣿⠀⣾⣿⡇⠀⢸⣿⡿⠀⠀⡀⠙⣿⣿⡆
⠀⠀⢠⣿⣿⣿⠿⣿⣿⣿⡄⠀⠀⠀ ⠙⢿⣿⣿⠇⠈⠿⣿⣿⡿⠋⠀⠀⢿⣿⡿⠁⠀⢸⣿⣿⣿⡇⢸⣿⣿⠀⣿⣿⣄⣾⣿⠛⠛⣿⣿⢠⣿⣿⣿ ⣼⣿⣿⣿ ⣿⣿⡿⠋⠀
⠀⢀⣾⠟⠋⠀⠀⠀⠙⠻⣷⡀⠀⠀
 
  v0.6.10

🔍 Detected coverage file: coverage.xml
🔍 Detected coverage file: .coverage
⚠️ Coverage reporter does not yet know how to process this file: .coverage
⭐️ Running in parallel mode. You must call the webhook after all jobs finish: `coveralls done --build-number 2273d1eb5872c5787013508[28](https://github.com/opsmill/infrahub/actions/runs/8750760687/job/24014957367?pr=2918#step:12:29)8d5a633c9573f5c`
  ·job_flag: backend-integration
🚀 Posting coverage data to https://coveralls.io/api/v1/jobs
---
✅ API Response: {"message":"Coverage for parallel build uploaded","url":"https://coveralls.io/builds/67014828"}
- 💛, Coveralls
 

@pjhoberman
Copy link

We're also experiencing this issue again. I opened a new issue: #124

@afinetooth
Copy link
Member

All, just doing some housekeeping:

  • @pjhoberman I am following up on your issue in Unable to upload report using coverage-reporter v0.6.10 #124
  • @jan-janssen aere you still experiencing any issues? I see in Unable to upload report using coverage-reporter v0.6.10 #124 that you resolved your issue by using coverage xml (converting coverage.py's .coverage output file to coverage.xml and using the cobertura parser with format: cobertura (or --format cobertura). That is in fact our recommendation because that non-standard-format .coverage file (a SQLite3 database) is hard to parse and our beta parser was struggling with it. We've updated our pytest-cov parser since to use coverage from your environment and perform that same conversion (via coverage xml), then send it through our cobertura (XML) parser.

@jan-janssen
Copy link

@afinetooth The coverage xml command fixed the issue for me, so I am fine.

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

Successfully merging a pull request may close this issue.

7 participants