Closed
Bug 1552964
Opened 5 years ago
Closed 5 years ago
Cannot run ./mach robocop locally
Categories
(Testing :: Mochitest, defect)
Tracking
(firefox69 fixed)
RESOLVED
FIXED
mozilla69
Tracking | Status | |
---|---|---|
firefox69 | --- | fixed |
People
(Reporter: TYLin, Assigned: TYLin)
References
(Regression)
Details
Attachments
(1 file)
I paste my log here.
$ ./mach robocop
/home/tlin/Projects/gecko/obj-fennec/backend.TestManifestBackend is out of date with respect to /home/tlin/Projects/gecko/testing/mochitest/mach_commands.py
Test configuration changed. Regenerating backend.
Re-install Firefox? (Y/n) n
Error running mach:
['robocop']
The error occurred in the implementation of the invoked mach command.
This should never occur and is likely a bug in the implementation of that
command.
You can invoke |./mach busted| to check if this issue is already on file. If it
isn't, please use |./mach busted file| to report it. If |./mach busted| is
misbehaving, you can also inspect the dependencies of bug 1543241.
If filing a bug, please include the full output of mach, including this error
message.
The details of the failure are as follows:
TypeError: run_robocop_test() takes exactly 3 arguments (110 given)
File "/home/tlin/Projects/gecko/testing/mochitest/mach_commands.py", line 579, in run_robocop
return mochitest.run_robocop_test(self._mach_context, tests, 'robocop', **kwargs)
Assignee | ||
Comment 1•5 years ago
|
||
I think we'll need to remove 'robocop'
from return mochitest.run_robocop_test(self._mach_context, tests, 'robocop', **kwargs)
Assignee | ||
Comment 2•5 years ago
|
||
Pushed by ahalberstadt@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c03edb23edaa
Remove the third argument passed to run_robocop_test(). r=ahal
Comment 4•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox69:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
Updated•5 years ago
|
Assignee: nobody → aethanyc
Updated•3 years ago
|
Has Regression Range: --- → yes
You need to log in
before you can comment on or make changes to this bug.
Description
•