android-emulator-runner icon indicating copy to clipboard operation
android-emulator-runner copied to clipboard

Unknown platform error occurred when running the UTP test suite. Please check logs for details.

Open bartekpacia opened this issue 2 years ago • 3 comments
trafficstars

Please see this workflow run: https://github.com/leancodepl/patrol/actions/runs/3910783889

What's the cause of this problem? It makes my tests too unreliable. I already have much memory and RAM assigned to the emulator.

UTP - Universal Test Platform (source)

bartekpacia avatar Jan 13 '23 12:01 bartekpacia

Hi, @bartekpacia! I recently encountered the same problem. I want to run my auto tests on one of my devices from device farm. I connect to the device remotely and use the command patrol develop --target integration_test/it1/it1_test.dat -d xxx.xxx.xx.xxx:7409, but I get the following output:

июл. 10, 2024 4:02:17 PM com.android.tools.utp.plugins.host.additionaltestoutput.AndroidAdditionalTestOutputPlugin deviceShellAndCheckSuccess
    WARNING: Shell command failed (1): ls "/sdcard/Android/media/****/additional_test_output"
    ls: /sdcard/Android/media/*******/additional_test_output: No such file or directory  
    июл. 10, 2024 4:02:17 PM com.android.tools.utp.plugins.host.additionaltestoutput.AndroidAdditionalTestOutputPlugin afterAll
    WARNING: Failed to retrieve additional test outputs from device.
    com.android.ddmlib.SyncException: Remote object doesn't exist!
            at com.android.ddmlib.SyncService.pullFile(SyncService.java:341)
            at com.android.ddmlib.internal.DeviceImpl.pullFile(DeviceImpl.java:1083)
            at com.android.tools.utp.plugins.deviceprovider.ddmlib.DdmlibAndroidDevice.pullFile(DdmlibAndroidDevice.kt)
            at com.android.tools.utp.plugins.deviceprovider.ddmlib.DdmlibAndroidDeviceController.pull(DdmlibAndroidDeviceController.kt:254)
            at com.google.testing.platform.executor.DeviceControllerProxy$pull$2.invoke(DeviceControllerProxy.kt:82)
            at com.google.testing.platform.executor.DeviceControllerProxy$pull$2.invoke(DeviceControllerProxy.kt:82)
            at com.google.testing.platform.core.telemetry.common.noop.NoopDiagnosticsScope.recordEvent(NoopDiagnosticsScope.kt:35)
            at com.google.testing.platform.core.telemetry.TelemetryKt.recordEvent(Telemetry.kt:66)
            at com.google.testing.platform.executor.DeviceControllerProxy.pull(DeviceControllerProxy.kt:79)
            at com.android.tools.utp.plugins.host.additionaltestoutput.AndroidAdditionalTestOutputPlugin.copyAdditionalTestOutputsFromDeviceToHost(AndroidAdditionalTestOutputPlugin.kt:222)
      
    
    Platform error occurred when running the UTP test suite
    : 
    : Test results saved as file:/Users/medrejting/StudioProjects/******/build/app/outputs/androidTest-results/connected/flavors/stageGoogle/sdk_gphone64_x86_64%20-%2014/test-result.pb. Inspect these results in Android Studio by selecting Run > Import Tests From File from the menu bar and importing test-result.pb.
    : 
    : > Task :app:connectedStageGoogleDebugAndroidTest FAILED
    : 
    : Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
    : 
    : You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
    : 
    : See https://docs.gradle.org/7.4/userguide/command_line_interface.html#sec:command_line_warnings
    : 725 actionable tasks: 6 executed, 719 up-to-date
    
    FAILURE: Build failed with an exception.
    
    * What went wrong:
    Execution failed for task ':app:connectedStageGoogleDebugAndroidTest'.
    See the report at: file:///Users/******/StudioProjects/******/build/app/reports/androidTests/connected/flavors/stageGoogle/index.html
    
    * Try:
    > Run with --stacktrace option to get the stack trace.
    > Run with --info or --debug option to get more log output.
    > Run with --scan to get full insights.
    
    * Get more help at https://help.gradle.org
    
    BUILD FAILED in 2m 16s 

Moreover, if you run the patrol develop command locally not on a remote device, then everything works. And if you run the flutter run command, just to launch the application for a remote device, it also works. Can you tell me how to solve this problem?

EskinaKseniya avatar Jul 11 '24 13:07 EskinaKseniya

Hey @EskinaKseniya, unfortunately I have no idea what the fix could be in this case 🥲

Also, I no longer work on Patrol.

bartekpacia avatar Jul 11 '24 13:07 bartekpacia

Ooh, it's sad🥲 Thanks for the answer!!

EskinaKseniya avatar Jul 11 '24 13:07 EskinaKseniya