Repository navigation
When a pre-run test or decorator (such as AndroidJitEmulatorDecorator) fails before Tradefed executes any test modules, LocalTestFlow wraps the underlying exception in TR_FAILED_TO_RUN_DEVICE_PRE_RUN_TEST_IN_LOCAL_TEST_FLOW. Because NewMultiCommandRequestHandler previously extracted only Throwable::getMessage when populating CommandDetail.error_message, the ATS Web UI error details (OMNILAB_ERROR) displayed only the outer wrapper message and dropped the Caused by chain. Additionally, CloudOrchestratorClient omitted the target endpoint URL in its exception messages when HTTP requests failed. - #7092
Merged
Merged
Conversation
copybara-service
Bot
force-pushed
the
test_1001670500
branch
4 times, most recently
from
October 26, 2026 10:21
ddce59f to
bac63a5
Compare
…r`) fails before Tradefed executes any test modules, `LocalTestFlow` wraps the underlying exception in `TR_FAILED_TO_RUN_DEVICE_PRE_RUN_TEST_IN_LOCAL_TEST_FLOW`. Because `NewMultiCommandRequestHandler` previously extracted only `Throwable::getMessage` when populating `CommandDetail.error_message`, the ATS Web UI error details (`OMNILAB_ERROR`) displayed only the outer wrapper message and dropped the `Caused by` chain. Additionally, `CloudOrchestratorClient` omitted the target endpoint URL in its exception messages when HTTP requests failed. Serialize the full exception causal chain and stack trace via `Throwables.getStackTraceAsString` in `NewMultiCommandRequestHandler` when building failed test and job error messages, and include the target endpoint URL in `CloudOrchestratorClient` request failure messages so connection and HTTP errors are immediately actionable in the ATS UI and logs. PiperOrigin-RevId: 1007151024
copybara-service
Bot
force-pushed
the
test_1001670500
branch
from
October 26, 2026 10:31
bac63a5 to
295e09b
Compare
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.
When a pre-run test or decorator (such as
AndroidJitEmulatorDecorator) fails before Tradefed executes any test modules,LocalTestFlowwraps the underlying exception inTR_FAILED_TO_RUN_DEVICE_PRE_RUN_TEST_IN_LOCAL_TEST_FLOW. BecauseNewMultiCommandRequestHandlerpreviously extracted onlyThrowable::getMessagewhen populatingCommandDetail.error_message, the ATS Web UI error details (OMNILAB_ERROR) displayed only the outer wrapper message and dropped theCaused bychain. Additionally,CloudOrchestratorClientomitted the target endpoint URL in its exception messages when HTTP requests failed.Serialize the full exception causal chain and stack trace via
Throwables.getStackTraceAsStringinNewMultiCommandRequestHandlerwhen building failed test and job error messages, and include the target endpoint URL inCloudOrchestratorClientrequest failure messages so connection and HTTP errors are immediately actionable in the ATS UI and logs.