Can no longer use --jsdebugger with ./mach test
Categories
(Firefox Build System :: Mach Core, enhancement)
Tracking
(firefox70 fixed)
Tracking | Status | |
---|---|---|
firefox70 | --- | fixed |
People
(Reporter: jdescottes, Assigned: egao)
References
Details
Attachments
(1 file, 1 obsolete file)
When using --jsdebugger with ./mach test, the command logs
Debugger must be specified with '=' when invoking ./mach test.
I suppose this check was added for the "debugger" argument and is wrongly matching and throwing for "jsdebugger"?
Assignee | ||
Comment 1•6 years ago
|
||
I know there was some work done in 1517811 that supersedes my changes in 1504550. Could you try pulling most recent m-c changes and see if that resolves the issue?
Assignee | ||
Comment 2•6 years ago
|
||
I went ahead and using the current tip, ran the following:
./mach test mochitest --jsdebugger
was able to reproduce the issue:
egao-44538:mozilla-central egao$ ./mach test mochitest --jsdebugger
Debugger must be specified with '=' when invoking ./mach test.
Please correct the command and try again.
egao-44538:mozilla-central egao$
Assignee | ||
Comment 3•6 years ago
|
||
- add jsdebugger to false positive list
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 4•6 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 5•5 years ago
|
||
Assignee | ||
Comment 6•5 years ago
|
||
I have what I believe is a much better solution.
It adds the --debugger
argument to the mach test
command provider (it has been lacking the --debugger
that explicit test harness command providers such as mochitest
and wpt
have).
The presence of --debugger
argument in the parsed Namespace
object can then be used to determine if the debugger is installed on system.
Reporter | ||
Comment 8•5 years ago
|
||
Thank you so much for working on this, your fix works perfectly!
Comment 9•5 years ago
|
||
bugherder |
Description
•