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

The uploaded report in the codeclimate shows error in the 'STATE' and no coverage is recorded #383

Open
kenware opened this issue Jan 21, 2019 · 2 comments
Assignees

Comments

@kenware
Copy link

kenware commented Jan 21, 2019

screen shot 2019-01-21 at 9 59 55 pm

screen shot 2019-01-21 at 10 00 22 pm

The circleci says the report is submitted successfully in the codeclimate but the uploaded report have error in the STATE column and no coverage is written in the batch.

screen shot 2019-01-21 at 10 04 25 pm

@efueger
Copy link
Member

efueger commented Jan 22, 2019

Hi @kenware -

Happy to help! I checked the logs and found this error message:


Details: {"error"=>{"class"=>"CC::Wally::Batch::TestFileReportsBatch::InvalidTestFileReport", "message"=>"Invalid path part \"\"", "file_document"=>"{\"_id\"=>BSON::ObjectId('5c463605ca36fb4d0c0020d8'), \"type\"=>\"test_file_reports\", \"blob_id\"=>\"4bccac1139f0bf48f819de54207339882c115b69\", \"coverage\"=>\"[null,null,null,null,null,null,0,0,null,0,0,0,null,0,0,0,0,null,null,0,0,null,0,0,0,0,null,null,null,null,null,null,0,0]\", \"covered_percent\"=>0, \"covered_strength\"=>0, \"line_counts\"=>{\"missed\"=>17, \"covered\"=>0, \"total\"=>17}, \"path\"=>\**"/usr/local/lib/python3.6/_bootlocale.py\"**, \"test_report_id\"=>BSON::ObjectId('5c463605c952c2169a00176d')}"}}

  • this is the important part: "path"=>"/usr/local/lib/python3.6/_bootlocale.py"

Your CircleCI output shows:

image

-> Can you try excluding that file from your tests?

Let me know once you've had a chance to do that! I'll be standing by to take another look.

@wfleming
Copy link
Contributor

This is a dupe of #375, which explains in more detail what leads to this and some things to consider for fixing it.

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

No branches or pull requests

4 participants