1260547 - Some trigger_runs.py calls take several minutes to complete, operate silently

Status: RESOLVED WONTFIX

(Testing Graveyard :: Autophone, defect)

Description

[Geoff Brown [:gbrown]]

I noticed this using the 'trigger' command in 'mach autophone', but I think it is a more general concern for all trigger_runs users. 

I notice the worst delays when using mozilla-inbound. For example, "python trigger_runs.py --repo=mozilla-inbound --build-location=tinderbox latest" prints:

Connecting to autophone server...

immediately (good) but then seems to hang for 2+ minutes before printing:

autophone-triggerjobs {"test_names": [], "build": "http://ftp.mozilla.org/pub/mozilla.org/mobile/tinderbox-builds/mozilla-inbound-android-api-15/1459279814/fennec-48.0a1.en-US.android-arm.apk", "devices": []}
- ok
autophone-triggerjobs {"test_names": [], "build": "http://ftp.mozilla.org/pub/mozilla.org/mobile/tinderbox-builds/mozilla-inbound-android-x86/1459279814/fennec-48.0a1.en-US.android-i386.apk", "devices": []}
- ok
exit
- 

I sometimes wonder if it is actually hung, ponder ctrl-c, etc.

It would be excellent if we could make this run faster. Otherwise, I'd like to provide a pleasant "hold on, we'll be right back" message.

Comment 1

[Bob Clary [:bc] (inactive)]

Autophone is going away. Resolving these to wontfix.