Skip to content
Common Workflows

NVMe Command constant needs to use full path #17

Sign in to view logs

NVMe Command constant needs to use full path

NVMe Command constant needs to use full path #17

Triggered via pull request November 15, 2024 06:19
@karthikk92karthikk92
synchronize #53
nvme_update
Status Failure
Total duration 1m 32s
Artifacts –

common-workflows.yaml

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

Annotations

2 errors
Golang Validation / Lint golang code: gonvme_tcp_fc.go#L66
var-naming: don't use underscores in Go names; var nvme_path should be nvmePath (revive)
Golang Validation / Lint golang code
issues found