Skip to content

Update method of determining the deployment in which a pod belongs #9

Update method of determining the deployment in which a pod belongs

Update method of determining the deployment in which a pod belongs #9

Triggered via push February 10, 2025 16:14
Status Failure
Total duration 39s
Artifacts

CI.yaml

on: push
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

16 errors
Test on ubuntu-latest, Python 3.9
Process completed with exit code 2.
Test on ubuntu-latest, Python 3.10
Process completed with exit code 2.
Test on ubuntu-latest, Python 3.11
The job was canceled because "ubuntu-latest_3_9" failed.
Test on ubuntu-latest, Python 3.11
Process completed with exit code 2.
Test on macOS-latest, Python 3.10
The job was canceled because "ubuntu-latest_3_9" failed.
Test on macOS-latest, Python 3.9
The job was canceled because "ubuntu-latest_3_9" failed.
Test on macOS-latest, Python 3.11
The job was canceled because "ubuntu-latest_3_9" failed.
Test on windows-latest, Python 3.9
The job was canceled because "ubuntu-latest_3_9" failed.
Test on windows-latest, Python 3.9
The operation was canceled.
Test on windows-latest, Python 3.9
Could not find micromamba activate test in C:\Users\runneradmin\.bash_profile
Test on windows-latest, Python 3.11
The job was canceled because "ubuntu-latest_3_9" failed.
Test on windows-latest, Python 3.11
Could not find micromamba activate test in C:\Users\runneradmin\.bash_profile
Test on windows-latest, Python 3.11
The operation was canceled.
Test on windows-latest, Python 3.10
The job was canceled because "ubuntu-latest_3_9" failed.
Test on windows-latest, Python 3.10
The operation was canceled.
Test on windows-latest, Python 3.10
Could not find micromamba activate test in C:\Users\runneradmin\.bash_profile