Skip to content

feat: add memory limiter to drop data when a soft limit is reached #3111

feat: add memory limiter to drop data when a soft limit is reached

feat: add memory limiter to drop data when a soft limit is reached #3111

Triggered via pull request November 27, 2024 05:54
Status Failure
Total duration 16m 45s
Artifacts 2

e2e.yaml

on: pull_request
Matrix: kubernetes-test
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 12 warnings
kubernetes-test (1.23, helm-chart)
Process completed with exit code 1.
kubernetes-test (1.30, helm-chart)
Process completed with exit code 1.
kubernetes-test (1.20.15, multi-apps)
Process completed with exit code 1.
kubernetes-test (1.23, cli-upgrade)
Process completed with exit code 1.
kubernetes-test (1.20.15, cli-upgrade)
Process completed with exit code 1.
kubernetes-test (1.20.15, helm-chart)
Process completed with exit code 1.
kubernetes-test (1.30, multi-apps)
Process completed with exit code 1.
kubernetes-test (1.23, multi-apps)
Process completed with exit code 1.
kubernetes-test (1.30, cli-upgrade)
Process completed with exit code 1.
kubernetes-test (1.23, workload-lifecycle)
Process completed with exit code 1.
kubernetes-test (1.20.15, workload-lifecycle)
Process completed with exit code 1.
kubernetes-test (1.30, workload-lifecycle)
Process completed with exit code 1.
kubernetes-test (1.23, helm-chart)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0
kubernetes-test (1.30, helm-chart)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0
kubernetes-test (1.20.15, multi-apps)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0
kubernetes-test (1.23, cli-upgrade)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0
kubernetes-test (1.20.15, cli-upgrade)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0
kubernetes-test (1.20.15, helm-chart)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0
kubernetes-test (1.30, multi-apps)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0
kubernetes-test (1.23, multi-apps)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0
kubernetes-test (1.30, cli-upgrade)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0
kubernetes-test (1.23, workload-lifecycle)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0
kubernetes-test (1.20.15, workload-lifecycle)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0
kubernetes-test (1.30, workload-lifecycle)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0

Artifacts

Produced during runtime
Name Size
odigos-cli
26.4 MB
odigos-images
286 MB