1424742 - UITests failures due to timeout error: Failed to execute block because idling resources below are busy.

Status: RESOLVED FIXED

(Firefox for iOS :: Build & Test, enhancement)

Description

[Isabel Rios[:isabel_rios]]

UI Tests are failing intermittently on master lately. 
There seems to be timing issues making the tests fail.

- Exception Details: Error Trace: [ { "Description" : "Failed to execute block because idling resources below are busy.", "Description Glossary" : { "GREYAppStateTracker" : "Waiting for gesture recognizer to detect or fail an ongoing gesture. Waiting for UIView's draw/layout pass to complete. A draw/layout pass normally completes in the next runloop drain. Full state transition call stack for all objects

- Exception Details: Error Trace: [ { "Description" : "Failed to execute block because idling resources below are busy.", "Description Glossary" : { "GREYAppStateTracker" : "Waiting for network requests to finish. By default, EarlGrey tracks all network requests. 

We will investigate the GREYConfiguration to check if changing default values will help to solve these issues

Comment 1

[Isabel Rios[:isabel_rios]]

Attachment: Pull Request

Not sure if this solution is similar to what you had in mind. Please give me your thoughts. We got two times in a row, one in iPhone and one in iPad sim, all tests passing. Although it also could be thanks to the low workload on bb today...
https://dashboard.buddybuild.com/apps/57bf25c0f096bc01001e21e0/build/5a2ed243717a2400012eef18

Comment 2

[No-Jun Park [:njpark]]

Comment on attachment 8936280 [details] [review]
Pull Request

LGTM, it fails for a different reason now, but at least it's not idle resource issue. It's probably timing issue that we can handle.

Comment 3

[Isabel Rios[:isabel_rios]]

Thanks for the review!
Merged: https://github.com/mozilla-mobile/firefox-ios/commit/fdd4d6858ef6cb2b1a74d180b63c89e8864022fc

Comment 4

[Isabel Rios[:isabel_rios]]

This issue was usually seen on master, but in v10.x it happens although much less frequently...wondering if we should uplift this?
Last failed v10.x build:
https://dashboard.buddybuild.com/apps/57bf25c0f096bc01001e21e0/build/5a332ca02167d10001b6de5c/test/f065c0cf-c5f2-4210-9074-a8180c56b345/6608e8ad-8cc0-4ff8-aef2-5590f459408a

Comment 5

[No-Jun Park [:njpark]]

Since this happens less frequently in v10,x, I think it's best if we just leave it and let it be included in v11.  No need to uplift to v10.x