-
Notifications
You must be signed in to change notification settings - Fork 54
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
🌱 add Github action to capture logs and pod descriptions when e2e fails #1510
🌱 add Github action to capture logs and pod descriptions when e2e fails #1510
Conversation
✅ Deploy Preview for olmv1 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Just a note that our e2e action should already have logic to upload artifacts upon failure. For example, https://github.com/operator-framework/operator-controller/actions/runs/11746095340 The artifacts are gathered by operator-controller/test/e2e/cluster_extension_install_test.go Lines 865 to 991 in e51c0c2
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1510 +/- ##
=======================================
Coverage 74.68% 74.68%
=======================================
Files 42 42
Lines 3271 3271
=======================================
Hits 2443 2443
Misses 652 652
Partials 176 176
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
I see that, but IHMO it is not so straightforward way helpful as looking the logs in the action. I do not see any harm to add it but if you folks see any reason for not please let me know. |
IMO, we should not have two different ways of doing this. If we can improve on what's there, great! If we need to replace what we already have with an alternate method, let's make sure we pull in the folks that were involved with the original implementation to make sure there we account for everything that was originally considered. For example, was there some specific reason that we did NOT use a log-based approach? |
Fair enough. |
Description
Reviewer Checklist