Skip to content

Fix TestRecvfdClosesSingleFile #6099

Fix TestRecvfdClosesSingleFile

Fix TestRecvfdClosesSingleFile #6099

Triggered via pull request November 22, 2023 07:59
Status Success
Total duration 4m 45s
Artifacts

ci.yaml

on: pull_request
yamllint  /  yamllint
11s
yamllint / yamllint
golangci-lint  /  golangci-lint
45s
golangci-lint / golangci-lint
exclude-fmt-errorf  /  exclude-fmt-errorf
6s
exclude-fmt-errorf / exclude-fmt-errorf
restrict-nsm-deps  /  restrict-nsm-deps
5s
restrict-nsm-deps / restrict-nsm-deps
checkgomod  /  checkgomod
25s
checkgomod / checkgomod
gogenerate  /  gogenerate
38s
gogenerate / gogenerate
exclude-replace  /  excludereplace
5s
exclude-replace / excludereplace
Matrix: build-and-test / build-and-test
Matrix: code-cov
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 3 warnings
golangci-lint / golangci-lint
Cannot open: File exists
golangci-lint / golangci-lint
Cannot open: File exists
golangci-lint / golangci-lint
Cannot open: File exists
golangci-lint / golangci-lint
Cannot open: File exists
golangci-lint / golangci-lint
Cannot open: File exists
golangci-lint / golangci-lint
Cannot open: File exists
golangci-lint / golangci-lint
Cannot open: File exists
golangci-lint / golangci-lint
Cannot open: File exists
golangci-lint / golangci-lint
Cannot open: File exists
golangci-lint / golangci-lint
Cannot open: File exists
golangci-lint / golangci-lint
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
code-cov (ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
code-cov (macos-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/