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(deps): update module github.com/jstemmer/go-junit-report to v2 #36748

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 10, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/jstemmer/go-junit-report v1.0.0 -> v2.1.0 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

⚠️ MAJOR VERSION UPDATE ⚠️ - please manually update this package


Release Notes

jstemmer/go-junit-report (github.com/jstemmer/go-junit-report)

v2.1.0: Version 2.1.0

Compare Source

v2.1.0 changelog
  • Fix #​147: Make timestamps in generated report more accurate.
  • Fix #​140: Escape illegal XML characters in junit output.
  • Fix #​145: Handle build errors in test packages with the _test suffix.
  • Fix #​145: Don't ignore build errors that did not belong to a package.
  • Fix #​134: Json test output was not parsed correctly when using the -race flag in go test.
  • Add support for === NAME lines introduced in Go1.20
  • junit: Add File attribute to testsuite.
  • junit: Allow multiple properties with the same name.
  • junit: Add the Testsuites.WriteXML convenience method.

v2.0.0: Version 2.0.0

Compare Source

Changes since v1.0.0

  • Support for parsing go test -json output.
  • Distinguish between build/runtime errors and test failures.
  • JUnit report now includes output for all tests and benchmarks, and global output that doesn't belong to any test.
  • Use full Go package name in generated report instead of only last path segment.
  • Add support for reading skipped/failed benchmarks.
  • Add -subtest-mode flag to exclude or ignore results of subtest parent tests.
  • Add -in and -out flags for specifying input and output files respectively.
  • Add -iocopy flag to copy stdin directly to stdout.
  • Add -prop flags to set key/value properties in generated report.
  • Add -parser flag to switch between regular go test (default) and go test -json parsing.
  • Output in JUnit XML is written in <![CDATA[]]> tags for improved readability.
  • Add hostname, timestamp and id attributes to JUnit XML.
  • Improve accuracy of benchmark time calculation and update formatting in report.
  • No longer strip leading whitespace from test output.
  • The formatter and parser packages have been replaced with junit and parser/gotest packages respectively.
  • Add support for parsing lines longer than 64KiB.
  • The JUnit errors/failures attributes are now required fields.
  • Drop support for parsing pre-Go1.13 test output.
  • Deprecate -go-version flag.

Configuration

📅 Schedule: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependency-major-update Indicates a dependency major version bump label Dec 10, 2024
@renovate renovate bot requested a review from a team as a code owner December 10, 2024 05:10
@renovate renovate bot requested a review from andrzej-stencel December 10, 2024 05:10
@renovate renovate bot force-pushed the renovate/github.com-jstemmer-go-junit-report-2.x branch from 623eae3 to a2538c2 Compare December 10, 2024 10:49
Copy link
Contributor Author

renovate bot commented Dec 10, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: internal/tools/go.sum
Command failed: install-tool golang 1.22.0

@renovate renovate bot force-pushed the renovate/github.com-jstemmer-go-junit-report-2.x branch from a2538c2 to c5e438a Compare December 10, 2024 11:15
@andrzej-stencel andrzej-stencel added the Skip Changelog PRs that do not require a CHANGELOG.md entry label Dec 11, 2024
Copy link
Member

@andrzej-stencel andrzej-stencel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't used the JUnit output, I'm not sure how to verify it's still useful. Do we use that for anything?

@andrzej-stencel andrzej-stencel self-requested a review December 11, 2024 10:26
@andrzej-stencel
Copy link
Member

andrzej-stencel commented Dec 11, 2024

the make install-tools command results in go-junit-results binary being named .tools/v2 now. Not sure how to fix this?

$ git clean -xdf
$ make install-tools
$ ls .tools
addlicense  checkfile  crosslink  genqlient  goimports      gotestsum    issuegenerator  misspell  porto        v2
builder     chloggen   gci        gofumpt    golangci-lint  govulncheck  mdatagen        multimod  testifylint
$ .tools/v2 --version
go-junit-report v2.1.0-dev  (HEAD)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependency issue dependency-major-update Indicates a dependency major version bump internal/tools Skip Changelog PRs that do not require a CHANGELOG.md entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants