New issue
Advanced search Search tips

Issue 785444 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Cannot attach debugger to Junit tests run by test_runner.py

Project Member Reported by mheikal@chromium.org, Nov 15 2017

Issue description

//build/android/test_runner.py does not support a --wait-for-java-debugger option to pause the tests until a java debugger is attached. This means that running tests using the test_runner.py script (currently the only way to run tests), will not allow you to attach an Eclipse or Android Studio debugger and step through the code while it is running.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Nov 16 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/39ab136fd29694b2029e66aeefb4d3281fd24ecb

commit 39ab136fd29694b2029e66aeefb4d3281fd24ecb
Author: Mohamed Heikal <mheikal@google.com>
Date: Thu Nov 16 01:19:15 2017

Adds --debug-socket arg to Junit tests in test_runner.py

test_runner.py script now accepts an new argument for Junit tests,
namely --debug-socket. If provided, the running script
instructs the JVM to pause and wait for a debugger to be attached at the
provided port/address.

Bug:  785444 
Change-Id: I1be2915ee70a9406f98e5f34635c535277eb439e
Reviewed-on: https://chromium-review.googlesource.com/773019
Commit-Queue: Mohamed Heikal <mheikal@google.com>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516936}
[modify] https://crrev.com/39ab136fd29694b2029e66aeefb4d3281fd24ecb/build/android/pylib/junit/junit_test_instance.py
[modify] https://crrev.com/39ab136fd29694b2029e66aeefb4d3281fd24ecb/build/android/pylib/local/machine/local_machine_junit_test_run.py
[modify] https://crrev.com/39ab136fd29694b2029e66aeefb4d3281fd24ecb/build/android/test_runner.py

Status: Fixed (was: Untriaged)

Sign in to add a comment