Skip to content
compliance

Use per package global lock for container uploads instead of memory lock #23072

# to view logs

Use per package global lock for container uploads instead of memory lock

Use per package global lock for container uploads instead of memory lock #23072

Triggered via pull request October 11, 2024 07:08
@GiteaBotGiteaBot
synchronize #31860
lunny:lunny/lock_per_package
Status Success
Total duration 6m 49s
Artifacts –

pull-compliance.yml

on: pull_request
files-changed  /  detect
5s
files-changed / detect
lint-backend
5m 48s
lint-backend
lint-templates
0s
lint-templates
lint-yaml
0s
lint-yaml
lint-swagger
0s
lint-swagger
lint-spell
33s
lint-spell
lint-go-windows
5m 58s
lint-go-windows
lint-go-gogit
5m 24s
lint-go-gogit
checks-backend
2m 57s
checks-backend
frontend
0s
frontend
backend
6m 25s
backend
docs
0s
docs
actions
0s
actions
Fit to window
Zoom out
Zoom in

Annotations

4 errors
checks-backend
cannot use debug.SetCrashOutput (value of type func(f *os.File, opts debug.CrashOptions) error) as func(*os.File) error value in assignment
lint-go-gogit
cannot use debug.SetCrashOutput (value of type func(f *os.File, opts debug.CrashOptions) error) as func(*os.File) error value in assignment
lint-backend
cannot use debug.SetCrashOutput (value of type func(f *os.File, opts debug.CrashOptions) error) as func(*os.File) error value in assignment
lint-go-windows
cannot use debug.SetCrashOutput (value of type func(f *os.File, opts debug.CrashOptions) error) as func(*os.File) error value in assignment