Closed
Bug 1295357
Opened 9 years ago
Closed 7 years ago
mach talos-test doesn't support --log-no-times
Categories
(Testing :: Talos, defect)
Testing
Talos
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: MattN, Assigned: Bebe)
Details
Attachments
(1 file)
|
2.62 KB,
text/plain
|
Details |
> mach --log-no-times talos-test -a tp5o
leads to a failure with
> 16:06:38 INFO - run_tests.py: error: unrecognized arguments: talos-test
I think the problem is `sys.argv[2:]` in testing/talos/mach_commands.py
> return talos.run_test(sys.argv[2:])
A workaround seems to be --log-tbpl with --log-tbpl-compact which doesn't have timestamps.
| Assignee | ||
Comment 1•7 years ago
|
||
From help I see the mach command structure is:
```
mach talos-test -h
usage: mach [global arguments] talos-test [command arguments]
```
I think there are 2 issues here:
1. In testing/talos/mach_commands.py we hardcode and set as a parameter: all the parameters that mach receives from the command line. That results in `--log-no-times talos-test -a tp5o`
2. MozHarness is not processing the `[Global Arguments:]` that mach receives. As MozHarness sets up it's own logger if we have global arguments that set the logging level they are not parsed and processed by MozHarness
I would say as a solution here we would need to have a mix between the 2:
ex: Send to mozharness the global arguments to make sure it will process them and setup the correct options.
:jmaher :rwood any thoughts on how we should proceed ?
Assignee: nobody → bebe
Flags: needinfo?(rwood)
Flags: needinfo?(jmaher)
Comment 2•7 years ago
|
||
this is 2 years old and I haven't had requests for this since- I would like to resolve as wontfix and if we find more demand for this, we can revisit.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(rwood)
Flags: needinfo?(jmaher)
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•