Oliver Nelson [:oliverthor] Reporter
	Description • 9 years ago

While performing adhoc.bitbar runs this week, I've been encountering a timeout error on device-flashing many times consecutively before the run ultimately fails. Each search takes 10 minutes, up to 6, culminating in an hour before I can discover that my build will not perform.
I noticed Martijn bugged a similar issue which seemed to resolve itself:
* https://bugzilla.mozilla.org/show_bug.cgi?id=1171066

Here are the samples I collected by attempting adhocs today:
* http://jenkins1.qa.scl3.mozilla.com/view/UI/job/flame-kk.ui.adhoc.bitbar/88/console
* http://jenkins1.qa.scl3.mozilla.com/view/UI/job/flame-kk.ui.adhoc.bitbar/87/console
* http://jenkins1.qa.scl3.mozilla.com/view/UI/job/flame-kk.ui.adhoc.bitbar/86/console
* http://jenkins1.qa.scl3.mozilla.com/view/UI/job/flame-kk.ui.adhoc.bitbar/85/console

I'm curious if this is related to the volume of adhocs I had supplanted at that time, but it seemed a necessary course of action in order to observe issues surrounding bug 1172343; or rather, a design behavior plaguing bitbar runs. 
This currently has the effect of bottlenecking my automation reporting, so until this is resolved they may be sent out at later intervals in order to ensure test integrity.


Sample Traceback:
...
09:20:20 [Testdroid] - [ERROR] - Flashing device timed out after 600 seconds
09:20:20 [Testdroid] - [WARN] - null
09:20:25 [Testdroid] - Searching for devices...
09:20:25 [Testdroid] - [Codename: Flame]
09:20:25 [Testdroid] - [SIMs: 1]
09:20:25 [Testdroid] - Found 16 devices
09:20:25 [Testdroid] - Selected (locked) device 94f7ce17 (209)
09:20:25 [Testdroid] - Flashing device with https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-central-flame-kk-eng/2015/06/2015-06-10-01-02-01/flame-kk.zip and memory throttled at 319MB
09:30:28 [Testdroid] - [ERROR] - Flashing device timed out after 600 seconds
09:30:28 [Testdroid] - [WARN] - null
09:30:28 [Testdroid] - [ERROR] - Failed to find device!
09:30:28 FATAL: Device session is null
09:30:28 java.io.IOException: Device session is null
09:30:28 	at jenkins.plugins.testdroid.DeviceSessionWrapper.setUp(DeviceSessionWrapper.java:183)
09:30:28 	at hudson.model.Build$BuildExecution.doRun(Build.java:154)
09:30:28 	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)
09:30:28 	at hudson.model.Run.execute(Run.java:1759)
09:30:28 	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
09:30:28 	at hudson.model.ResourceController.execute(ResourceController.java:89)
09:30:28 	at hudson.model.Executor.run(Executor.java:240)

	Martijn Wargers (dead)
	Comment 1 • 9 years ago

This is not the same as bug 1172032? I guess we could also send a mail to bitbar support about this, but I haven't got response from bug 1172032, either.

	Martijn Wargers (dead)
	Comment 2 • 9 years ago

Now seeing this for flame-kk-319.b2g-inbound.tinderbox.ui.functional.smoke.bitbar jobs, see bug 1188298.

	Martijn Wargers (dead)
	Comment 3 • 9 years ago

Also non-smoke.1.bitbar seems to suffer from this.

	BMO Automation
	Comment 4 • 6 years ago

Firefox OS is not being worked on