brettchabot
brettchabot
The stack trace is confusing, because ClassesArgTokenizer should only be invoked much earlier in the test run, when the runner is deciding which class to run. It looks from the...
Oh wait, I think my diagnosis was wrong. I was looking at the wrong [AndroidJUnit4](https://github.com/android/android-test/blob/main/runner/android_junit_runner/java/androidx/test/runner/AndroidJUnit4.java#L66C1-L66C1) class. [ext.junit.AndroidJUnit4](https://github.com/android/android-test/blob/main/ext/junit/java/androidx/test/ext/junit/runners/AndroidJUnit4.java#L101) will always reparse the entire command line arguments. That seems wrong...
> The whole "started:/finished:" pre-test sequence is something that is new to runner:1.5.0. Can you explain in more detail this comment? The differences between runner 1.4 and 1.5 should be...
With this many variables at play and no repro case it will be difficult for me to diagnose exactly what is happening. It definitely seems suspicious for ClassesArgTokenizer to fail...
Please reopen if you are still having this issue with the latest alpha release https://developer.android.com/jetpack/androidx/versions/alpha-channel#january_26_2024
AJUR's algorithm is a fork of bazel's HashBackedStrategy. https://github.com/bazelbuild/bazel/blob/master/src/java_tools/junitrunner/java/com/google/testing/junit/runner/sharding/HashBackedShardingFilter.java However, I notice that the bazel default is a RoundRobinStrategy https://github.com/bazelbuild/bazel/blob/master/src/java_tools/junitrunner/java/com/google/testing/junit/runner/sharding/RoundRobinShardingFilter.java I cannot remember why the hash-backed algorithm was chosen for...
Sorry without more info its going to difficult for us to help. Have you tried looking at logcat output to see if there are any errors there? Can you share...
Please tell me if I'm missing something, but I don't see the logcat file. ``` ~/Downloads$ unzip -l connected.zip Archive: connected.zip Length Date Time Name --------- ---------- ----- ---- 0...
Ah thank you. I see this in the log when the test starts: ``` 08-18 17:08:01.958 23848 23908 I TestRunner: started: canLogOut(com.encircle.espresso.LoginTest) ``` So the test is running in process...
Is there a stack trace outputted on either the 'adb shell am instrument -w "com.encircle.test/androidx.test.runner.AndroidJUnitRunner' command or in logcat