Skip to content
[prom-fed] E2E CI

[main] Fix CRDs being installed even when they already exist and don't need updating #38

Sign in to view logs

[main] Fix CRDs being installed even when they already exist and don't need updating

[main] Fix CRDs being installed even when they already exist and don't need updating #38

Triggered via pull request October 24, 2024 21:28
@mallardduckmallardduck
opened #114
mallardduck:crd-install-bugfix
Status Failure
Total duration 10m 37s
Artifacts 2

prom-fed-e2e-ci.yaml

on: pull_request
Matrix: Prebuild needed Env vars
Matrix: e2e-prometheus-federator
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
e2e-prometheus-federator (arm64, v1.28.14-k3s1)
Process completed with exit code 1.
e2e-prometheus-federator (x64, v1.28.14-k3s1)
The job was canceled because "arm64_v1_28_14-k3s1" failed.
e2e-prometheus-federator (x64, v1.28.14-k3s1)
Process completed with exit code 1.
e2e-prometheus-federator (arm64, v1.28.14-k3s1)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v4, azure/setup-kubectl@v3, azure/setup-helm@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "artifacts-arm64-v1.28.14-k3s1", "artifacts-x64-v1.28.14-k3s1". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Artifacts

Produced during runtime
Name Size
artifacts-arm64-v1.28.14-k3s1 Expired
468 KB
artifacts-x64-v1.28.14-k3s1 Expired
469 KB