Closed
Bug 1260547
Opened 8 years ago
Closed 6 years ago
Some trigger_runs.py calls take several minutes to complete, operate silently
Categories
(Testing Graveyard :: Autophone, defect)
Testing Graveyard
Autophone
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: gbrown, Unassigned)
References
Details
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•6 years ago
|
||
Autophone is going away. Resolving these to wontfix.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Updated•2 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•