[NDB PERMISSION_DENIED error] Fix trusty stacktrace on ANDROID_EMULATOR#5375
Merged
Conversation
dylanjew
approved these changes
Jul 22, 2026
dylanjew
approved these changes
Jul 23, 2026
javanlacerda
approved these changes
Jul 23, 2026
This was referenced Jul 24, 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
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.
This PR comes as a need after the revert of this #5339 PR which introduced short circuit mechanisms to avoid DB queries, this however proved to provoke issues, so short circuit is no longer an option to fix any PERMISION_DENIED erros.
When we run jobs with an
ANDROID_EMULATORjobs, they all fail after executing a testcase. This happens becauseANDROID_EMULATORplatform goes trough some legacy code(before the pre/main/pos separation of tasks) which expects the current bot to have access to DB or GCS.This error only appear for
uworkersand doesn't happen forpre-emptiblebots. Because pre-emptibles do contain a trusted service account, where as uworkers dont.Changes
Test performed
Changes initially present in dev since July 13th, and it didn't seem to non brake anything under ANDROID_EMULATOR jobs. Now for
ANDROID_EMULATORjobs.Before:

After:
