-
Notifications
You must be signed in to change notification settings - Fork 49
CodeCov Upload Error Message #203
Comments
Submitted an issue codecov/codecov-python#129. Submitted to the wrong repo at first, deleted that comment. |
Great job @johlju - sorry I haven't had time to look into this (have had to do actual "work work" over the break - lots of work on creating security layers around CosmosDb and API Management). This month might be a bit slow on the DSC side from me unfortunately due to too many other commitments 😢 |
@PlagueHO No worries. Sorry to hear you had a lot of work over the holidays :/ This month will be a bit slower for me as well, after this week at least. Still on vacation, back at work on the 8th and have a deadline at end of January. |
i have the same issue. |
first time i look at your code but IMHO the only meaningful change i see around those dates is that one. |
So a colleague visually debugged this for me. It seems that it could be this row that is problem. It is not allowed to run |
interesting ! now that you're saying this i compared my old/working codecov output:
with the current/non-working one:
...and it seems you're right (or close at least). |
but that change occurred more than 2 years ago ? |
maybe found something: |
It was just a possible issue. Our thought was that something changed in Window (how Python is calling this
But the 'root' row you found could be it too. |
That is all some interesting info. I did confirm that this issue also occurs when executing locally (I had to trick the machine into pretending to be AppVeyor by defining some environment variables that the CodeCov.io looks for). But as this issue seems to be mostly harmless I didn't get much further. But it would be great to resolve. I think @johlju's suggestion that this could be caused by running from PowerShell instead of CMD could be a big possibility. But what might have changed was the version of Python and the behavior of the "try_to_run()" function. I'm thinking that this error may have always occurred, it is just the error never got pushed into the error stream so we never saw it. But I am just guessing - because I can't see any other change that could have caused this. |
FYI i manually patched the line i was talking about right after doing |
@PlagueHO What do think about switching to this .exe report uploader for Codecov. It seems that the prerequisites 'Chocolatey' is installed on the build worker.
I just saw it, so I haven't done anything more than read the README.md. |
The problem seems to escalate, now more errors are shown. The errors still does not affect functionality (yet). https://ci.appveyor.com/project/PowerShell/xpowershellexecutionpolicy/build/1.0.66.0#L279 |
Good idea, but it looks like the CodeCov.exe uses the same Python code to upload the report. So we're seeing the same issue. Such a pain! |
Oh, I hoped it did not do that :/ |
The Ruby one looks like it might work - Choco can be used to install Ruby pretty easily. Great ideas! |
Oh wait - I missed the message from @ramlongcat - great idea there. Might be worth looking into more. Thanks @ramlongcat and sorry I didn't see your post. What do you think @johlju |
I’m all for the idea, if it solves the problem. :) Fixing the problem in the script at source I think would be the best option. Parsing the script at our end could maybe be problematic if changes occurs at source? |
- Fix codecov no longer generates an error message when uploading test coverage (issue PowerShell#203).
Looks like |
- Fix codecov no longer generates an error message when uploading test coverage (issue PowerShell#203).
- Changes to CodeCovIo - Fix codecov no longer generates an error message when uploading test coverage (issue #203).
An error has recently started appearing during upload of the code coverage results to CodeCov.io. This error appears to not actually prevent upload or fail the build, so is not critical.
The error occurs when calling the
codecov
Python script from this line of theCodeCovIo
module.The output of the
codecov
python can be seen in theCodeCovUpload.log
artifact stored in the AppVeyor build artifacts. This shows no errors:It also shows the artifact being uploaded. The result can also be seen in CodeCov.io.
The error seems to occur or be outputted into the error stream somewhere in this Python code:
https://github.com/codecov/codecov-python/blob/master/codecov/__init__.py
The last changes to this code was made 5 days ago. looking back through AppVeyor logs, this error started appearing at least 4 days ago but not more than 6 days ago - so this would track with the recent changes made to the CodeCov Python.
This is occurring in all repos that process and upload code coverage.
The text was updated successfully, but these errors were encountered: