Fix debendabot bumps in root & /test directory#653
Merged
amacaskill merged 1 commit intoGoogleCloudPlatform:mainfrom Jun 2, 2025
Merged
Fix debendabot bumps in root & /test directory#653amacaskill merged 1 commit intoGoogleCloudPlatform:mainfrom
amacaskill merged 1 commit intoGoogleCloudPlatform:mainfrom
Conversation
hungnguyen243
force-pushed
the
fixDependabotBump
branch
from
7226cf3 to
fb62941
Compare
hungnguyen243
force-pushed
the
fixDependabotBump
branch
from
fb62941 to
c987621
Compare
amacaskill
approved these changes
Jun 2, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
This PR fixes a build issue with e2e test encountered with #609 (reverted). On top of changes already in the aforementioned PR, I added context.Context argument to e2ejob.WaitForJobFailed() to fix the build issue due to client-go upgrade. I did a local E2E test run of a random test and it was successful.
Which issue(s) this PR fixes:
Fixes #609
Special notes for your reviewer:
Does this PR introduce a user-facing change?: