Skip to content
CI

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

Sign in to view logs

Bug: ensure we watch health probes in dnsrecord controller

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

Triggered via pull request November 15, 2024 14:46
@maksymvavilovmaksymvavilov
synchronize #308
gh-264
Status Failure
Total duration 3m 58s
Artifacts –

ci.yaml

on: pull_request
lint
2m 42s
lint
Verify code
1m 15s
Verify code
Verify manifests
42s
Verify manifests
Verify bundle
1m 20s
Verify bundle
Verify helm build
1m 25s
Verify helm build
Verify imports
31s
Verify imports
Verify generate
45s
Verify generate
Verify go.mod
13s
Verify go.mod
Unit Test Suite
2m 19s
Unit Test Suite
Integration Test Suite
3m 46s
Integration Test Suite
Fit to window
Zoom out
Zoom in

Annotations

11 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
Integration Test Suite
Process completed with exit code 2.
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