Fix verify test errors on main branch#552
Merged
hungnguyen243 merged 3 commits intoGoogleCloudPlatform:mainfrom Apr 9, 2025
Merged
Fix verify test errors on main branch#552hungnguyen243 merged 3 commits intoGoogleCloudPlatform:mainfrom
hungnguyen243 merged 3 commits intoGoogleCloudPlatform:mainfrom
Conversation
hungnguyen243
force-pushed
the
addWICheckForNode
branch
from
fca7009 to
8b18a7e
Compare
hungnguyen243
changed the title
amacaskill
approved these changes
Apr 9, 2025
This was referenced Apr 9, 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?
/kind failing-test
What this PR does / why we need it:
The verify test is failing in main branch since the CI test failed to scan these failures due to a bug with go mod in /test directory. We fixed the CI bug in #554.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: