You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever a E2E test fails in PR check, it is hard to determine what actually happened in case the test times out.
Goal of this issue is to get logs of deployment that the failed test uses and archive it in the workflow page for download.
This way we are able closely to debug issues with container startup.
Implementation ideas
In order to implement this we need to look at AfterAll() function of the tests and retrieve the logs from minikube.
Something like:
forEach failed test get the deployment and retrievelogs kubectl get pods -n sonataflow-operator-system | grep relevant ones kubectl logs -f orderprocessing-7899775db4-ff6nj -n sonataflow-operator-system > failed_test_case_1_depoyment_logs
The text was updated successfully, but these errors were encountered:
Description
Whenever a E2E test fails in PR check, it is hard to determine what actually happened in case the test times out.
Goal of this issue is to get logs of deployment that the failed test uses and archive it in the workflow page for download.
This way we are able closely to debug issues with container startup.
Implementation ideas
In order to implement this we need to look at AfterAll() function of the tests and retrieve the logs from minikube.
Something like:
forEach failed test get the deployment and retrievelogs
kubectl get pods -n sonataflow-operator-system | grep relevant ones
kubectl logs -f orderprocessing-7899775db4-ff6nj -n sonataflow-operator-system > failed_test_case_1_depoyment_logs
The text was updated successfully, but these errors were encountered: