InfrastructureFailure when running Jetpack Compose Android UI tests

Question & Answer Builds
1

Bitrise Build Issue Report template

Description of the issue

We were facing issues with our Android jetpack compose tests in CircleCI so we decided to try out Bitrise. We have been trying to get our Android UI Compose tests to run on the pipeline but we keep facing infrastructure failure.
Link to the log: Bitrise - Mobile Continuous Integration and Delivery - iOS & Android Build Automation
We also tried using the higher machine size since this could be due to the machine. We also switched between different ways of running UI tests as shown in various examples in the community shared videos.

Environment:

On Bitrise, Default stack, Android and docker on ubuntu 20.04

If on Bitrise.io: which stack? If not on Bitrise.io: on what operating system? (Plus any other information you can share)

Which build Step causes the issue and which version of the step?

Virtual Device testing for Android.

Reproducibility

  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • Does the issue happen sporadically, or every time? : Everytime
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? : It has been a week since we have been trying to get this working, we have currently disabled all UI tests on our pipelines, it’d great if we can get some help with this.

Build log

Configs:

  • AppPath: /bitrise/deploy/app-dev-debug.apk
  • TestTimeout: 900.000000
  • FlakyTestAttempts: 3
  • DownloadTestResults: true
  • DirectoriesToPull:
  • AutoGoogleLogin: false
  • EnvironmentVariables:
  • ObbFilesList:
  • TestDevices:

Model API Level Locale Orientation
Pixel2 29 en portrait

  • TestType: instrumentation
  • TestApkPath: /bitrise/deploy/app-dev-debug-androidTest.apk
  • InstTestPackageID:
  • InstTestRunnerClass:
  • InstTestTargets:
  • UseOrchestrator: false
    Uploading app and test files
    App path (/bitrise/deploy/app-dev-debug.apk), is bundle: false
    Assets requested: {isBundle:false testApp: Apk:{UploadURL: GcsPath: Filename:app-dev-debug.apk} Aab:{UploadURL: GcsPath: Filename:} TestApk:{UploadURL: GcsPath: Filename:app-dev-debug-androidTest.apk} RoboScript:{UploadURL: GcsPath: Filename:} ObbFiles:}
    Uploading file(/bitrise/deploy/app-dev-debug.apk) to (gs://bitrise-addon-ftl-prod-bucket/android-tests/aa98f296-e330-47d4-bd0f-ab38865c4398/app.apk)
    => Files uploaded
    Starting test
    AndroidInstrumentationTest: &{AppApk:0xc0004be000 AppBundle: AppPackageId: OrchestratorOption:DO_NOT_USE_ORCHESTRATOR ShardingOption: TestApk:0xc0004be040 TestPackageId: TestRunnerClass: TestTargets: ForceSendFields: NullFields:}
    => Test started
    Waiting for test results
  • Validating
  • (1/1) running
  • (0/1) running
    => Test finished
    Test results:
    Model API Level Locale Orientation Outcome
    Pixel2 29 en portrait inconclusive(InfrastructureFailure)
    Downloading test assets
    => Assets downloaded
    The downloaded test assets path (/tmp/vdtesting_test_assets1603747096) is exported to the VDTESTING_DOWNLOADED_FILES_DIR environment variable.
2

Any idea what the issue is, this will block us from using this in prod with a paid account for multiple apps. Please some light over here would be great.

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.