Skip to content

Use same build ID retrieval mechanism as the agent #66

Use same build ID retrieval mechanism as the agent

Use same build ID retrieval mechanism as the agent #66

Triggered via pull request January 21, 2025 13:04
@branczbrancz
synchronize #24
common-buildid
Status Failure
Total duration 1m 48s
Artifacts

build.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 3 warnings
Go Build: cmd/parca-debuginfo/main.go#L588
G115: integer overflow conversion int -> uint64 (gosec)
Go Build: cmd/parca-debuginfo/main.go#L260
Magic number: 0o755, in <argument> detected (mnd)
Go Build: cmd/parca-debuginfo/main.go#L579
Magic number: 4, in <condition> detected (mnd)
Go Build: cmd/parca-debuginfo/main.go#L584
Magic number: 3, in <operation> detected (mnd)
Go Build: cmd/parca-debuginfo/main.go#L187
avoid direct access to proto field shouldInitiate.ShouldInitiateUpload, use shouldInitiate.GetShouldInitiateUpload() instead (protogetter)
Go Build: cmd/parca-debuginfo/main.go#L221
avoid direct access to proto field initiationResp.UploadInstructions.UploadStrategy, use initiationResp.GetUploadInstructions().GetUploadStrategy() instead (protogetter)
Go Build
issues found
Skip check
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Go Build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Go Build
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2