-
Notifications
You must be signed in to change notification settings - Fork 69
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
test(e2e): fix indentation for dump logs #26
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/test
Completing without getting the E2E tests to pass as this change should not non-impactful on the actual suites, and verified the fix to the flow works as desired. |
Fixes #
Description
@tallaxes noticed that the log dump on failure was not working.
Looking into it I noticed that the action was not indented correctly. This PR fixes the indentation, and the issues with the log dump.
How was this change tested?
I ran the E2E pipeline with a guaranteed failure [in drift] with the log dumps current status in main, which caused it to fail:
https://github.com/Azure/karpenter/actions/runs/6829122309/job/18574667354
Then I ran it with the guaranteed failure [in drift] with the log dump indentation fixed:
https://github.com/Azure/karpenter/actions/runs/6829114912
The fixed indentation executed correctly.
*
Does this change impact docs?
Release Note