Set slogger on rungroup after logshipping is set up, so that rungroup logs will be shipped #1119
Triggered via pull request
September 17, 2024 16:25
RebeccaMahany
Status
Failure
Total duration
3m 58s
Artifacts
–
lint.yml
on: pull_request
Matrix: lint
Matrix: govulncheck
lint_mergeable
0s
Annotations
10 errors
|
lint (windows-latest)
too many arguments in call to rungroup.NewRunGroup\n\thave (*slog.Logger)\n\twant ())"
|
|
lint (windows-latest)
too many arguments in call to rungroup.NewRunGroup\n\thave (*slog.Logger)\n\twant ())"
|
|
lint (windows-latest)
too many arguments in call to rungroup.NewRunGroup\n\thave (*slog.Logger)\n\twant ()"
|
|
lint (windows-latest)
golangci-lint exit with code 3
|
|
lint (windows-latest)
too many arguments in call to rungroup.NewRunGroup\n\thave (*slog.Logger)\n\twant ())"
|
|
lint (windows-latest)
too many arguments in call to rungroup.NewRunGroup\n\thave (*slog.Logger)\n\twant ())"
|
|
lint (windows-latest)
too many arguments in call to rungroup.NewRunGroup\n\thave (*slog.Logger)\n\twant ()"
|
|
lint (windows-latest)
Process completed with exit code 1.
|
|
govulncheck (windows-latest):
ee/watchdog/watchdog_service_windows.go#L230
too many arguments in call to rungroup.NewRunGroup
|
|
govulncheck (windows-latest)
Process completed with exit code 1.
|