Error in reader.js about kover-report HOT 10 CLOSED

I was able to work around it by reverting to v1.

False positive. The build succeeded once, then started failing again, even with v1.

from kover-report.

@humblehacker Thanks for creating the issue! Could you mabe post your kover report.xml file here? Because it might be an issue related to parsing and reading that file as far I can see from your logs.

from kover-report.

Thanks for your reply 😄 I'd rather not publicly post the coverage report. I thought maybe I could uncover the issue by replacing the contents of report.xml in your repo with my coverage file and running the test parse kover report from xml file. I wasn't expecting the test to pass of course, but I thought it might produce the same exception and I could catch it in the debugger. Unfortunately, parsing succeeded!

Do you have any other ideas on how I could debug this on my end?

from kover-report.

It seems that whatever issue is triggering this problem is transient in the generation of report.xml. I thought maybe my test above didn't give me the results I was looking for because I had generated the coverage file locally, while the failure occurred on GitHub Actions. Maybe there was something about the different platform that was causing a problem with the generated file. So I updated my workflow to save the file as an artifact. However, when the workflow ran, kover-report did not fail!

So I guess I leave it like this for now. If I do encounter the failure again, at least I'll have access to the problematic XML file and maybe then we can find the cause.

from kover-report.

Thanks for the insights! I will close this issue now, but feel free to come back to it if you encounter this error again

from kover-report.

@mi-kas The error has reoccured, and this time I've got the xml file involved. But when I try my trick of using it in your unit test parse kover report from xml file, parsing appears to succeed.

from kover-report.

@humblehacker I just released a new beta version with a fix that I think might solve your issue. Could you try to use mi-kas/[email protected] in your action and let me know if the error still occurs?

from kover-report.

Thanks for the quick response! I'll give this a try and let you know. Since it's a transient issue, it'll take a few clean builds before I'll be able to give a fairly certain 👍

from kover-report.

@humblehacker Did you encounter the issue again?

from kover-report.

@humblehacker I will close this issue now, but feel free to come back to it if you encounter the error again in your builds.

from kover-report.