Closed
Bug 1214739
Opened 9 years ago
Closed 9 years ago
Autophone - disable Talos except on try
Categories
(Testing Graveyard :: Autophone, defect)
Testing Graveyard
Autophone
Tracking
(firefox44 affected)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox44 | --- | affected |
People
(Reporter: bc, Assigned: bc)
References
Details
Attachments
(1 file, 1 obsolete file)
674 bytes,
patch
|
jmaher
:
review+
|
Details | Diff | Splinter Review |
Until we can resolve the Talos/adb issues, we should disable it except on try.
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8673767 -
Flags: review?(jmaher)
Comment 2•9 years ago
|
||
missing the patch. question though- do we really want this on try? can I push to try with a build or try-extend a job to run this on it? I want to make sure this is useful.
Assignee | ||
Comment 3•9 years ago
|
||
It would help if the patch file wasn't empty.
Attachment #8673767 -
Attachment is obsolete: true
Attachment #8673767 -
Flags: review?(jmaher)
Attachment #8673768 -
Flags: review?(jmaher)
Updated•9 years ago
|
Attachment #8673768 -
Flags: review?(jmaher) → review+
Assignee | ||
Comment 4•9 years ago
|
||
I thought this would be useful if we want to test work arounds for the issues with the talos jobs without having to put it into normal production in order to test the ideas. The use case is there is a a try build, one that already exists or one you created. You can use the command line trigger on autophone to submit the try build for test autophone-talos which will only run on device nexus-7-jss15q-2. Something like python trigger_runs.py --build-location=tinderbox --repo=try --test=autophone-talos --build-url=http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/bclary@mozilla.com-570afbabbeeb/try-android-api-11/
Assignee | ||
Comment 5•9 years ago
|
||
https://github.com/mozilla/autophone/commit/4c7617667d5c32b1a4cce0f8ef45daf272476f12
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
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
•