Closed
Bug 1310820
Opened 8 years ago
Closed 8 years ago
Trychooser puts unescaped spaces within arguments
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1295219
People
(Reporter: bytesized, Unassigned)
Details
Since tests are not run by default in Windows 8, I need to select the option to "Restrict tests to platform: Win8". Unfortunately, this generates a command with unescaped spaces in arguments. For example: > ./mach try -b o -p win64 -u mochitest-bc[Windows 8],mochitest-e10s-bc[Windows 8] -t none[Windows 8] If I try to execute this, I get an error: > It looks like you passed an unrecognized argument into mach. > > The try command does not accept the arguments: 8] I believe that the command given should escape the spaces or quote the arguments.
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•