Skip to content

fix stringer failures #380

fix stringer failures

fix stringer failures #380

Triggered via push October 21, 2025 14:22
Status Failure
Total duration 5m 9s
Artifacts

ci.yml

on: push
Matrix: Run Tests
Build Repo
0s
Build Repo
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 11 warnings, and 1 notice
Lint
issues found
Run Tests (windows-2019)
Windows Server 2019 has been retired. The Windows Server 2019 image has been removed as of 2025-06-30. For more details, see https://github.com/actions/runner-images/issues/12045
Lint
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0fZf3aAAAAAC0aIzmGbm1RrigC8a4yHMlQ0hJMzBFREdFMDExMwBFZGdl
Lint: pkg/security/grantvmgroupaccess.go#L2
redundant-build-tag: The build tag "// +build" is redundant since Go 1.17 and can be removed (revive)
Lint: pkg/security/grantvmgroupaccess_test.go#L2
redundant-build-tag: The build tag "// +build" is redundant since Go 1.17 and can be removed (revive)
Lint: pkg/process/syscall.go#L2
redundant-build-tag: The build tag "// +build" is redundant since Go 1.17 and can be removed (revive)
Lint: pkg/process/process.go#L2
redundant-build-tag: The build tag "// +build" is redundant since Go 1.17 and can be removed (revive)
Lint: wim/validate/main_windows.go#L2
redundant-build-tag: The build tag "// +build" is redundant since Go 1.17 and can be removed (revive)
Lint: wim/decompress.go#L2
redundant-build-tag: The build tag "// +build" is redundant since Go 1.17 and can be removed (revive)
Lint: wim/wim.go#L2
redundant-build-tag: The build tag "// +build" is redundant since Go 1.17 and can be removed (revive)
Lint: wim/lzx/lzx.go#L160
redefines-builtin-id: redefinition of the built-in function max (revive)
Lint: wim/lzx/lzx.go#L156
redefines-builtin-id: redefinition of the built-in function max (revive)
Lint
Failed to restore: Cache service responded with 400
Run Tests (windows-2019)
The windows-2019 runner image is being deprecated, consider switching to windows-2022(windows-latest) or windows-2025 instead. For more details see https://github.com/actions/runner-images/issues/12045.