Virtual-device-testing-for-ios fails with no error message

#1

Description of the issue

virtual-device-testing-for-ios fails with no error message.
From the video recorded by Firebase Testlab I can see that the app is installed on a device, but the runtime logs are empty.

Running the same test directly in Firebase Test Lab results in timeout termination after 5 minutes, which is not sufficient for the tests in question. The tests require around 20 minutes to finish. I wonder if Bitrise integration has the same 5 minute time cap (there is no error message indicating it).

Environment:

Where did the issue happen?

Bitrise.io (10.2 Stack)

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

virtual-device-testing-for-ios 0.9.5

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? : Every time
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? :

Local reproduction

Was able to reproduce it locally.

Build log

+------------------------------------------------------------------------------+

| (2) virtual-device-testing-for-ios@0.9.5                                     |
+------------------------------------------------------------------------------+
| id: virtual-device-testing-for-ios                                           |
| version: 0.9.5                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: go                                                                  |
| time: 2019-07-31T10:15:12Z                                                   |
+------------------------------------------------------------------------------+
|                                                                              |
INFO[10:15:12]  * [OK] Step dependency (go) installed, available. 
Configs:
- ZipPath: /Users/vagrant/build/testbundle.zip
- TestTimeout: 900
- TestDevices:
---
Model     OS version   Orientation   Locale   
iphonex   12.0         portrait      en       
---
Upload IPAs
=> .xctestrun uploaded
Start test
=> Test started
Waiting for test results
- Validating
- (1/1) running
- (0/1) running
=> Test finished
Test results:
Model     OS version   Orientation   Locale   Outcome                        
iphonex   12.0         portrait      en       failure(TimedOut)   
|                                                                              |
+---+---------------------------------------------------------------+----------+
| x | virtual-device-testing-for-ios@0.9.5 (exit code: 1)           | 19.2 min |
+---+---------------------------------------------------------------+----------+
| Issue tracker: ...itrise-steplib/steps-virtual-device-testing-for-ios/issues |
| Source: ...//github.com/bitrise-steplib/steps-virtual-device-testing-for-ios |
+---+---------------------------------------------------------------+----------+
0 Likes

#2

Hi there @nderkach-toptal! In your test results you should be able to find a logcat file in which we can look at the emulator’s detailed logs. Could you please send me that file? Thanks! :smile:

0 Likes

#3

Hi! How do I find that logcat file? The only thing is see in log artifacts is a video recording and the Logs tab is empty.

0 Likes

#4

Hi there @nderkach-toptal!

You can find your logs by going to your Bitrise account’s dashboard, selecting the app in question, and then the build which has the issue itself. Once you found the intended build, you should see the logs, along with the “Download Logs” button:

Please download this and send it to us, so we can take a closer look :wink:

0 Likes

closed #5

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

0 Likes