Skip to content

run odigos diagnose on e2e tests failure #2148

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

Closed
edeNFed opened this issue Jan 7, 2025 · 2 comments
Closed

run odigos diagnose on e2e tests failure #2148

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

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
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale label Mar 17, 2025
@github-actions github-actions bot removed the stale label Mar 24, 2025
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

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

No branches or pull requests

2 participants