Skip to content
Common Workflows

NVMe Command constant needs to use full path #11

Sign in to view logs

NVMe Command constant needs to use full path

NVMe Command constant needs to use full path #11

Triggered via pull request November 14, 2024 14:33
@donatworkdonatwork
synchronize #53
nvme_update
Status Failure
Total duration 1m 5s
Artifacts –

common-workflows.yaml

on: pull_request
Golang Validation  /  Lint golang code
15s
Golang Validation / Lint golang code
Golang Validation  /  Yaml Lint
5s
Golang Validation / Yaml Lint
Quality Checks  /  Unit tests and package coverage
24s
Quality Checks / Unit tests and package coverage
Quality Checks  /  GoSec
29s
Quality Checks / GoSec
Quality Checks  /  Go Formatter and Vetter
24s
Quality Checks / Go Formatter and Vetter
Quality Checks  /  Malware Scan
54s
Quality Checks / Malware Scan
Fit to window
Zoom out
Zoom in

Annotations

2 errors
Golang Validation / Lint golang code: gonvme_tcp_fc.go#L76
G204: Subprocess launched with a potential tainted input or cmd arguments (gosec)
Golang Validation / Lint golang code
issues found