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 junit output for vuln report #1518

Merged
merged 1 commit into from
Dec 17, 2024
Merged

Conversation

czunker
Copy link
Contributor

@czunker czunker commented Dec 17, 2024

I tried it with the container image ubuntu:noble-20240114. Then the unit output currently get's this new section:

	<testsuite name="Vulnerability Report for ubuntu:noble-20240114@9069f132fbe5" tests="2" failures="2" errors="0" id="0" time="">
		<properties>
			<property name="report.packages.total" value="90"></property>
			<property name="report.packages.critical" value="0"></property>
			<property name="report.packages.high" value="2"></property>
			<property name="report.packages.medium" value="0"></property>
			<property name="report.packages.low" value="0"></property>
			<property name="report.packages.none" value="0"></property>
		</properties>
		<testcase name="libssl3" classname="vulnerability">
			<failure message="Update libssl3"><![CDATA[libssl3 with version3.0.10-1ubuntu3 has known vulnerabilities (score 7.5)]]></failure>
		</testcase>
		<testcase name="libc6" classname="vulnerability">
			<failure message="Update libc6 to 2.39-0ubuntu8.3"><![CDATA[libc6 with version2.38-3ubuntu1 has known vulnerabilities (score 7.3)]]></failure>
		</testcase>
	</testsuite>

Copy link
Contributor

Test Results

  1 files   27 suites   1m 0s ⏱️
509 tests 508 ✅ 1 💤 0 ❌
510 runs  509 ✅ 1 💤 0 ❌

Results for commit 7ad8ecc.

@czunker czunker merged commit 739104b into main Dec 17, 2024
15 checks passed
@czunker czunker deleted the czunker/fix_junit_vuln_report branch December 17, 2024 10:06
@github-actions github-actions bot locked and limited conversation to collaborators Dec 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants