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

fix: don't write invalid characters in report files #482

Merged
merged 1 commit into from
Dec 28, 2021
Merged

Conversation

fsamin
Copy link
Member

@fsamin fsamin commented Dec 28, 2021

and fix the IS_TTY option

closes #454

Signed-off-by: francois samin francois.samin@corp.ovh.com

and fix the IS_TTY option

closes #454

Signed-off-by: francois  samin <francois.samin@corp.ovh.com>
@sonarcloud
Copy link

sonarcloud bot commented Dec 28, 2021

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

66.7% 66.7% Coverage
0.0% 0.0% Duplication

@richardlt richardlt merged commit 9404945 into master Dec 28, 2021
@fsamin fsamin deleted the fix_xml_cdata branch December 28, 2021 15:27
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Invalid XML character in jUnit reports in case of failure
2 participants