-
Notifications
You must be signed in to change notification settings - Fork 13
bug: Fix log that is checked in A/B update e2e test #383
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
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.
Pull request overview
This PR fixes a bug in the A/B update e2e test by correcting the log message pattern that is checked in the test. The change updates the expected stderr message from "Staging of update 'AbUpdate' succeeded" to "Staging of A/B update succeeded" to match the actual output format.
Key Changes
- Updated the string check in
triggerTridentUpdateto look for "Staging of A/B update succeeded" instead of "Staging of update 'AbUpdate' succeeded"
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
🔍 Description
ab_update.gois checking for an outdated log from Trident.Also, add separate
stageandfinalizetesting to-cipipeline so we catch failures faster.