Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Archive logs of failed E2E test cases in PR checks #352

Open
domhanak opened this issue Jan 16, 2024 · 4 comments
Open

Archive logs of failed E2E test cases in PR checks #352

domhanak opened this issue Jan 16, 2024 · 4 comments

Comments

@domhanak
Copy link
Contributor

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

@domhanak
Copy link
Contributor Author

@ricardozanini @jakubschwan FYI, not sure how this connects with BDD test migration now, but same feature should be available there.

@ricardozanini
Copy link
Member

@domhanak the BDD is archiving everything in testbdd/logs. Including all the pods logs involved in the test.

@domhanak
Copy link
Contributor Author

Great so we just need to make sure it gets uploaded to Pr check space so it is available for contributors and involved pull requests users.

I will update the tasks description.

@ricardozanini
Copy link
Member

Relates to #324

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants