ci: temporarily disable gdrive behavior tests#7385
Merged
Conversation
dosubot
Bot
added
size:XS
PsiACE
approved these changes
Apr 14, 2026
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.
Which issue does this PR close?
Related to #7384.
Rationale for this change
Google Drive behavior tests are currently not reliable enough to keep enabled in CI. We already have
#6684tracking non-deterministic listing behavior after writes, and the behavior test suite itself already documents Google Drive abuse-detection redirect loops for some list/delete-heavy cases.Because the behavior workflow schedules gdrive across core and all bindings, a single unstable service can block the whole matrix.
What changes are included in this PR?
This change removes
gdrivefrom the behavior-test planner so it is no longer scheduled for core or binding behavior jobs. It also adds a planner test to lock that behavior in place until the underlying gdrive issue is fixed.Are there any user-facing changes?
No user-facing API changes. This only changes CI scheduling.
AI Usage Statement
Used AI-assisted editing and validation during implementation.