Skip to content
Common Workflows

NVMe Command constant needs to use full path #6

Sign in to view logs

NVMe Command constant needs to use full path

NVMe Command constant needs to use full path #6

Triggered via pull request November 14, 2024 06:41
@rishabhatdellrishabhatdell
synchronize #53
nvme_update
Status Failure
Total duration 55s
Artifacts –

common-workflows.yaml

on: pull_request
Golang Validation  /  Lint golang code
26s
Golang Validation / Lint golang code
Golang Validation  /  Yaml Lint
5s
Golang Validation / Yaml Lint
Quality Checks  /  Unit tests and package coverage
26s
Quality Checks / Unit tests and package coverage
Quality Checks  /  GoSec
28s
Quality Checks / GoSec
Quality Checks  /  Go Formatter and Vetter
22s
Quality Checks / Go Formatter and Vetter
Quality Checks  /  Malware Scan
46s
Quality Checks / Malware Scan
Fit to window
Zoom out
Zoom in

Annotations

4 errors
Golang Validation / Lint golang code: gonvme_tcp_fc.go#L91
G204: Subprocess launched with a potential tainted input or cmd arguments (gosec)
Golang Validation / Lint golang code: gonvme_tcp_fc_test.go#L16
G204: Subprocess launched with a potential tainted input or cmd arguments (gosec)
Golang Validation / Lint golang code: gonvme_tcp_fc_test.go#L22
unused-parameter: parameter 't' seems to be unused, consider removing or renaming it as _ (revive)
Golang Validation / Lint golang code
issues found