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

Parse error in Azure from junit output #4918

Closed
1 task done
merijnrats opened this issue May 21, 2024 · 3 comments
Closed
1 task done

Parse error in Azure from junit output #4918

merijnrats opened this issue May 21, 2024 · 3 comments

Comments

@merijnrats
Copy link

What kind of issue is this?

  • PlatformIO Core.
    If you’ve found a bug, please provide an information below.

Configuration

Operating system:
Windows
PlatformIO Version:
6.1.15

Description of problem

there seems to be a bug with the formatting of the junit-output, there aren't any new lines or spacings and because of that Azure can't parse the xml.

Steps to Reproduce

  1. pio test --junit-output-path .

Actual Results

wrong

Expected Results

correct

Additional info

I have a fix and I will try to create merge request as suggestion for devs

@ivankravets
Copy link
Member

Spaces should not be a cause of the issue. Could you debug in depth this issue and find the problem?

@merijnrats
Copy link
Author

pipeline
pipelinefail
I want to run the unittest with junit output to insert the test results into the pipeline results. But I get a utf-8 parse error and since the current results are in 1 line I figured that would lead to the parse error which in my tested fixed it after adding newlines and whitespaces.

But i've got a workaround where I output it to json and run a custom script to parse it to junit which i can insert into Azure so it's fine,

@ivankravets
Copy link
Member

utf-8 parse error

UTF-8 is de-facto standard encoding. If the system does not support it, you need to tune your system. You can also add extra step and convert from UTF-8 to "encoding supported by OS".

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

No branches or pull requests

2 participants