Closed Bug 755929 Opened 14 years ago Closed 14 years ago

allow results_url and datazilla_url, etc to specify a local file path vs a file:// URL

Categories

(Testing :: Talos, defect)

Product:
Testing
Component:
Talos
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: k0scist, Unassigned)

Details

Instructing developers how to run talos, there was a lot of confusion and wasted time explaining the structure of a file:// url on windows. Why bother using them? If we have a http:// https:// url we should post to it. Otherwise, it is probably a local file path. We can change the config option and text to be more appropriate, e.g. talos --results path/to/results.txt
with the landing of bug 755527 this should be much easier: a change in http://hg.mozilla.org/build/talos/file/45b903369dca/talos/output.py#l46 should be able to fix this for all formats we care about
Summary: allow results_url (later, raw_results_url) to specify a local file path vs a file:// URL → allow results_url and datazilla_url, etc to specify a local file path vs a file:// URL
It should also be possible to specify stdout (and not via /dev/stdout as that will only work on linux and similar)
This is now fixed
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.