执行失败的任务＆＃x27;：app：connecteddebugandroidtest＆＃x27;。 gitlab ci

Question

我正在使用gitlab ci测试我的APK，并且要做到这一点，我需要一个虚拟设备，以便我可以测试仪器测试以使用fastlane命令进行屏幕截图，但是当我尝试运行./gradlew connectedandroidtest时，使用此管道中的Gitlab中的gitectedAndroidTest，

   image: mingc/android-build-box:latest

stages:
  - ui-test
  - build
  - test

variables:
  LC_ALL: "en_US.UTF-8"
  LANG: "en_US.UTF-8"


before_script:
  - chmod +x ./gradlew
  - gem install fastlane
  - export JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64/
build:
 
  stage: build
  script:
    -  fastlane  build
  artifacts:
    paths:
      - "app/build/outputs/"
  tags:
    - docker
ui-test:
  stage: ui-test
  script:
    - export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/
    # Add missing folder to the PATH, to use sdkmanager
    - export ADB_INSTALL_TIMEOUT=30
    - export USE_SDK_WRAPPER=True
    # Insall and run emulator
    - sdkmanager "platform-tools" "platforms;android-27" "emulator"

    - sdkmanager "system-images;android-27;google_apis;arm64-v8a"
    - adb devices
    # Create an ARM-based emulator AVD with 250 MB SD car
    - echo "no" | avdmanager create avd -n Android_7.0_API_24 -k "system-images;android-27;google_apis;arm64-v8a" -c 250M --force

    # Check the image is properly created and available to run
    - emulator -list-avds
    - emulator -avd  Android_7.0_API_24 -no-audio -no-window -gpu off &
    - adb wait-for-device devices
    - echo "Emulator is ready"
    - adb devices
    - export JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64/
    - ./gradlew connectedAndroidTest
    - fastlane  screenshots

  tags:
    - docker
test:
  stage: test
  script:
    - fastlane  test
  tags:
    - docker
            

我得到了此错误即使我在Android Studio运行该测试时没有

[PropertyFetcher]: ShellCommandUnresponsiveException getting properties for device emulator-5554
java.lang.Throwable: ShellCommandUnresponsiveException getting properties for device emulator-5554
    at com.android.ddmlib.PropertyFetcher.handleException(PropertyFetcher.java:248)
    at com.android.ddmlib.PropertyFetcher.access$500(PropertyFetcher.java:30)
    at com.android.ddmlib.PropertyFetcher$1.run(PropertyFetcher.java:211)
Caused by: com.android.ddmlib.ShellCommandUnresponsiveException
    at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:689)
    at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:468)
    at com.android.ddmlib.internal.DeviceImpl.executeShellCommand(DeviceImpl.java:705)
    at com.android.ddmlib.PropertyFetcher$1.run(PropertyFetcher.java:207)
[PropertyFetcher]: ShellCommandUnresponsiveException getting properties for device emulator-5554
java.lang.Throwable: ShellCommandUnresponsiveException getting properties for device emulator-5554
    at com.android.ddmlib.PropertyFetcher.handleException(PropertyFetcher.java:248)
    at com.android.ddmlib.PropertyFetcher.access$500(PropertyFetcher.java:30)
    at com.android.ddmlib.PropertyFetcher$1.run(PropertyFetcher.java:211)
Caused by: com.android.ddmlib.ShellCommandUnresponsiveException
    at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:689)
    at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:468)
    at com.android.ddmlib.internal.DeviceImpl.executeShellCommand(DeviceImpl.java:705)
    at com.android.ddmlib.PropertyFetcher$1.run(PropertyFetcher.java:207)
> Task :app:connectedDebugAndroidTest
Skipping device 'Android_7.0_API_24(AVD)' for 'app:': Unknown API Level
 > : No compatible devices connected.[TestRunner] FAILED 
Found 1 connected device(s), 0 of which were compatible.
> Task :app:connectedDebugAndroidTest FAILED
FAILURE: Build failed with an exception.
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.2/userguide/command_line_interface.html#sec:command_line_warnings
61 actionable tasks: 61 executed
* What went wrong:
Execution failed for task ':app:connectedDebugAndroidTest'.
> There were failing tests. See the report at: file:///builds/chaimae.bousaid/myapplication/app/build/reports/androidTests/connected/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 6m 24s
Cleaning up project directory and file based variables
00:32
ERROR: Job failed: exit code 1

错误