Skip to content
CI

Bug: ensure we watch health probes in dnsrecord controller #983

Sign in to view logs

Bug: ensure we watch health probes in dnsrecord controller

Bug: ensure we watch health probes in dnsrecord controller #983

Triggered via pull request November 22, 2024 11:00
@maksymvavilovmaksymvavilov
synchronize #308
gh-264
Status Success
Total duration 4m 1s
Artifacts –

ci.yaml

on: pull_request
lint
2m 43s
lint
Verify code
1m 13s
Verify code
Verify manifests
45s
Verify manifests
Verify bundle
1m 14s
Verify bundle
Verify helm build
1m 16s
Verify helm build
Verify imports
25s
Verify imports
Verify generate
40s
Verify generate
Verify go.mod
15s
Verify go.mod
Unit Test Suite
2m 25s
Unit Test Suite
Integration Test Suite
3m 51s
Integration Test Suite
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
lint
Cannot open: File exists
lint
Cannot open: File exists
lint
Cannot open: File exists
lint
Cannot open: File exists
lint
Cannot open: File exists
lint
Cannot open: File exists
lint
Cannot open: File exists
lint
Cannot open: File exists
lint
Cannot open: File exists
lint
Cannot open: File exists
lint
The following actions use a deprecated Node.js version and will be forced to run on node20: golangci/golangci-lint-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
lint
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2