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.

Sign up for GitHub

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

Jump to bottom

run odigos diagnose on e2e tests failure #2148

Open
edeNFed opened this issue Jan 7, 2025 · 1 comment
Open

run odigos diagnose on e2e tests failure #2148

edeNFed opened this issue Jan 7, 2025 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@edeNFed
Copy link
Contributor

edeNFed commented Jan 7, 2025

To gain deeper insights into failed tests or debug flaky tests more effectively, it’s recommended to run the odigos diagnose command immediately after a test failure. Once completed, upload the resulting artifact to GitHub for seamless tracking and future investigation.
@edeNFed edeNFed added enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed labels Jan 7, 2025
@vordimous
Copy link

I would like to take on this issue. My understanding of the requirements are to update the E2E Test workflow to run the odigos diagnose command and collect the output as an artifact on the Action. I have done something similar with Docker diagnostic logs in an action before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vordimous @edeNFed