Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

CI tests are timing out #9829

Closed
tobrun opened this issue Aug 22, 2017 · 7 comments
Closed

CI tests are timing out #9829

tobrun opened this issue Aug 22, 2017 · 7 comments
Labels
Android Mapbox Maps SDK for Android

Comments

@tobrun
Copy link
Member

tobrun commented Aug 22, 2017

Since roughly 8 days, we have started to see that CI tests that are timing out. At first it looked the test were running slower but now noticing that some occurrences seem to stop execution. For now the android build has been made non required for merging.

ezgif com-video-to-gif 18

Capturing from the logs:

08-18 23:08:39.091: I/TestRunner(5106): failed: testBackgroundOpacityAsConstant(com.mapbox.mapboxsdk.testapp.style.BackgroundLayerTest)
08-18 23:08:39.091: I/TestRunner(5106): ----- begin exception -----
08-18 23:08:39.092: I/TestRunner(5106): java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=com.mapbox.mapboxsdk.testapp/.activity.espresso.EspressoTestActivity } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1503122874085 and now the last time the queue went idle was: 1503122874085. If these numbers are the same your activity might be hogging the event queue.
08-18 23:08:39.092: I/TestRunner(5106): 	at android.support.test.runner.MonitoringInstrumentation.startActivitySync(MonitoringInstrumentation.java:360)
08-18 23:08:39.092: I/TestRunner(5106): 	at android.support.test.rule.ActivityTestRule.launchActivity(ActivityTestRule.java:219)
08-18 23:08:39.092: I/TestRunner(5106): 	at android.support.test.rule.ActivityTestRule$ActivityStatement.evaluate(ActivityTestRule.java:268)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.Suite.runChild(Suite.java:128)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.Suite.runChild(Suite.java:27)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
08-18 23:08:39.092: I/TestRunner(5106): 	at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
08-18 23:08:39.092: I/TestRunner(5106): 	at android.support.test.internal.runner.TestExecutor.execute(TestExecutor.java:59)
08-18 23:08:39.092: I/TestRunner(5106): 	at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:262)
08-18 23:08:39.092: I/TestRunner(5106): 	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1853)
08-18 23:08:39.092: I/TestRunner(5106): ----- end exception -----
@tobrun tobrun added the Android Mapbox Maps SDK for Android label Aug 22, 2017
@tobrun tobrun added this to the android-v5.2.0 milestone Aug 22, 2017
@tobrun
Copy link
Member Author

tobrun commented Aug 23, 2017

This issue will be potentially fixed with #9816 as the source for this regression is cd8eb13

@brunoabinader
Copy link
Member

This will be fixed in #9842.

@jfirebaugh
Copy link
Contributor

@tobrun #9846 seems to show that cd8eb13 is not the issue (or at least not the only issue).

@tobrun
Copy link
Member Author

tobrun commented Aug 24, 2017

Apologies @brunoabinader @jfirebaugh tracked this down to a059c74. Reverting this change in #9851.

@jfirebaugh
Copy link
Contributor

💯 🙏 @tobrun for tracking that down.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Android Mapbox Maps SDK for Android
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants