getting INVALID(DETAILS_UNAVAILABLE) when running android ui testcases with bitrise

[gauravbansal-cpi]

Below are the logs for the last step when I am trying to run Android Instrumentation test cases with Bitrise. ------------------------------------------------------------------------------+

(5) virtual-device-testing-for-android@1.1.1	+------------------------------------------------------------------------------+	id: virtual-device-testing-for-android		version: 1.1.1		collection: https://github.com/bitrise-io/bitrise-steplib.git		toolkit: go		time: 2020-01-21T18:40:25Z	+------------------------------------------------------------------------------+

Configs:

• AppPath: /bitrise/deploy/ChargePoint_5.58.0-233-1434-qa-debug.apk
• TestTimeout: 900.000000
• FlakyTestAttempts: 0
• DownloadTestResults: false
• DirectoriesToPull: storage/sdcard/Pictures/screenshots
• AutoGoogleLogin: false
• EnvironmentVariables:
• ObbFilesList:

• TestDevices:

  Model API Level Locale Orientation
  Nexus10 22 en portrait

• TestType: instrumentation
• TestApkPath: /bitrise/deploy/ChargePoint_5.58.0-233-1434-qa-debug-androidTest.apk
• InstTestPackageID:
• InstTestRunnerClass: androidx.test.runner.AndroidJUnit4
• InstTestTargets:
• UseOrchestrator: false Uploading app and test files => Files uploaded Starting test => Test started Waiting for test results
• Validating Failed to get test status, error: Failed to get test status: INVALID(DETAILS_UNAVAILABLE) | | +---+---------------------------------------------------------------+----------+ | x | virtual-device-testing-for-android@1.1.1 (exit code: 1) | 21.67 sec| +---+---------------------------------------------------------------+----------+ | Issue tracker: ...se-steplib/steps-virtual-device-testing-for-android/issues | | Source: ...thub.com/bitrise-steplib/steps-virtual-device-testing-for-android | +---+---------------------------------------------------------------+----------+

[gauravbansal-cpi]

Below are the bitrise.yml details for this particular workflow

steps:

• activate-ssh-key@4.0.3: run_if: '{{getenv "SSH_RSA_PRIVATE_KEY" | ne ""}}'
• git-clone@4.0.14: inputs:
  • clone_depth: '1'
• install-missing-android-tools@2.3.6: inputs:
  • gradlew_path: "$PROJECT_LOCATION/gradlew"
• android-unit-test@1.0.0: inputs:
  • module: "$MODULE"
  • variant: "$VARIANT"
  • project_location: "$PROJECT_LOCATION"
• android-build-for-ui-testing@0.1.1: inputs:
  • variant: "$VARIANT"
  • project_location: "$PROJECT_LOCATION"
  • module: "$MODULE"
• virtual-device-testing-for-android@1.1.1: inputs:
  • test_devices: Nexus10,22,en,portrait
  • directories_to_pull: storage/sdcard/Pictures/screenshots
  • inst_test_runner_class: androidx.test.runner.AndroidJUnit4
  • test_type: instrumentation
• deploy-to-bitrise-io@1.9.5: inputs:
  • is_enable_public_page: 'false'
  • notify_user_groups: developers

[bitrise-coresteps-bot]

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

[bitrise-coresteps-bot]

I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.