Fix coverage submit

[jbmartin]

Not sure if this is a coveralls.io or coveralls-python issue, but on Travis everything seems to submit correctly (see below), yet on coveralls.io the commit coverage shows a questionmark.

==
Reporting 17 files
==
psiturk/__init__.py - 1/2
psiturk/__main__.py - 0/5
psiturk/amt_services.py - 0/504
psiturk/command_line.py - 0/67
psiturk/counter.py - 0/195
psiturk/db.py - 13/24
psiturk/experiment.py - 120/528
psiturk/experiment_errors.py - 12/44
psiturk/experiment_server.py - 0/65
psiturk/experiment_server_controller.py - 0/147
psiturk/models.py - 39/102
psiturk/psiturk_config.py - 22/61
psiturk/psiturk_org_services.py - 0/118
psiturk/psiturk_shell.py - 0/1430
psiturk/setup_example.py - 0/33
psiturk/user_utils.py - 18/52
psiturk/version.py - 1/2
Coverage submitted!
Job #39.1
https://coveralls.io/jobs/1412415
{u'url': u'https://coveralls.io/jobs/1412415', u'message': u'Job #39.1'}
Done. Your build exited with 0.

[spectras]

Hello there,

I have the same problem. I setup everything according to the help page, everything appears to work fine, the travis logs show coverage and coveralls running and the job appears on coveralls.io… but it says 0 file and is completely empty. What can I do to fix the issue?

[coagulant]

Have you tried reaching coveralls.io support?

If logs say coverage data is fine and http API correctly responded with job id, it's probably an issue on coveralls side.

Does the issue persist? Have you tried running coveralls outside of Travis (e.g. locally)? There is coveralls --debug command to test what payload is going to be generated and sent (requires env variables or .yml file if running outside of Travis).

[spectras]

Thanks for the fast answer. Well, it looks like something is wrong on coveralls.io side. Now every other refresh of coveralls.io interface, my repo does not even show up. The other refresh it show its name but cannot load it. I tried deleting my account a creating another one but, for some reason, I cannot manage to delete the account (it says ok, but if I login again, it still works).

Well, so I guess that was the wrong door to knock on :)

[cdeil]

We got the same issue here: https://github.com/astropy/photutils/pull/211#issuecomment-67165855

I've asked about this via the coveralls support web form and the answer was that the coverage data sent wasn't proper (without being more specific). Is there any way to debug / fix this?

[coagulant]

@cdeil yes, please use coveralls debug

[coagulant]

I'm closing this, considering it's coveralls.io temporary problems. Please reopen if you think this is coveralls-python bug. Please refer to https://github.com/coagulant/coveralls-python#troubleshooting first to obtain some info to work with.

Summary:

jbmartin experienced problem with data not displaying on coveralls.io spectras opened issue https://github.com/lemurheavy/coveralls-public/issues/418 (no response from coveralls team) cdeil contacted coveralls support via web form, but no concrete response was given