Report is not generated in pull request

Description

Report is not generated for pull request https://github.com/eclipse/kapua/pull/2801.

I also have one more opened pull request https://github.com/eclipse/kapua/pull/2797, and report is generated success on it. I didn’t change configuration files, or something similar in PR 2801.

Also, everything is up to date in PR 2801, and push has been done several times.

Hi @ct-anaalbic

Can you provide the commit SHA for the head of PR 2801? I grabbed the one we have in our database, 8734d4fd89962baea41b5cc459028d1eec5927c8, and I can’t locate it in our logs as having been uploaded.

Hi @drazisil

Where did you find that commit? Because in my log I can’t find it. SHA for the head commit of PR 2801 is 4ee89a185bf8ce5892aa659560d37ca5ed357663.

Regards.

Hi @ct-anaalbic I show 8734d4fd89962baea41b5cc459028d1eec5927c8 as the head of PR 2801 in our database, authored by you on branch jobEngineService-Refactoring at 2019-12-24 13:06:53

When I look up 4ee89a185bf8ce5892aa659560d37ca5ed357663, I see it also authored by you o the same branch around 2019-11-12 14:52:41

Both have the same commit message, but 8734d4fd89962baea41b5cc459028d1eec5927c8 is also showing as deleted, which may be why you can’t find it.

Both are showing they had an error processing, so let me look up 4ee89a185bf8ce5892aa659560d37ca5ed357663 and see what it was.

UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb4 in position 836685: invalid start byte

Here is the raw, uploaded report: https://codecov.io/codecov/v4/raw/2020-01-13/0ED464320D8D8700069E9466F2D59054/4ee89a185bf8ce5892aa659560d37ca5ed357663/3fc988ca-d92c-4220-855f-3c49bbce14a1.txt

Based on https://www.cl.cam.ac.uk/~mgk25/ucs/quotes.html, it seems your coverage reporter is returning a non-unicode “quote” mark.

Looks like there is something there that broke our processor.

Hi @drazisil,

so, do I have to wait for your response, or maybe to create other PR? I am not sure what I have to do in this situation, because it was very strange for me, I didn’t have the same problems.

Thank you and best regards!

Oh, sorry. That last line was supposed to be further up. This fix here is for you to convert the report to UTF-8 before uploading it, there is nothing we can can do on Codecov’s side to fix this.

What coverage reporter are you using? The docs for it may have instructions on how to make sure it outputs correctly?

Hi @drazisil,

Actually, we are using this in our project:

  <plugin>
            <groupId>org.jacoco</groupId>
            <artifactId>jacoco-maven-plugin</artifactId>
            <version>${jacoco.version}</version>
            <executions>
                <execution>
                    <id>default-prepare-agent</id>
                    <goals>
                        <goal>prepare-agent</goal>
                    </goals>
                </execution>
                <execution>
                    <id>default-report</id>
                    <phase>prepare-package</phase>
                    <goals>
                        <goal>report</goal>
                    </goals>
                </execution>
            </executions>
        </plugin> 

But I didn’t change anything in coverage reporter, or in codecov configuration. Do you maybe have some other solution? Because I have other pull requests with the same configuration, and report is generated correctly, without errors.

Also, when I try to see error, I can’t see description. I only have a view as on screenshot bellow:

So, do you have some other idea, or solution maybe?

Best regards.

If you want to provide another recent SHA, I can see if we still have the unicode error.

We are not currently exposing theses errors to the customer, correcting this is an OKR focus.

Do you think I have to create new pull request, or to send you another SHA from this PR?

Another SHA from the same PR should be fine.

Ok. This is SHA: 1aaccb6e097a3d372fbc7cc5c42fb813a55504f2.

Regards.

Same error

UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb4 in position 840004: invalid start byte

You will need to correct the encoding in your report before we can process it.