Closed
Bug 583142
Opened 14 years ago
Closed 14 years ago
mozrunner does not accept full path to binary on Mac OS X
Categories
(Testing :: Mozbase, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: k0scist, Assigned: harth)
Details
(Whiteboard: [mozmill-1.4.2-][mozmill-1.5.1+])
Attachments
(1 file)
630 bytes,
patch
|
cmtalbert
:
review+
|
Details | Diff | Splinter Review |
On OSX, if I run
mozmill -b /Volumes/Minefield/Minefield.app/Contents/MacOS/firefox-bin
I get an error:
/Volumes/Minefield/Minefield.app/Contents/MacOS/firefox-bin/Contents/MacOS/firefox-bin does not exist
it appends the Contents/MacOS/firefox-bin, trying to be clever. However, in this case it should be too clever. If the user specifies the full path to the binary, it shouldn't be that clever.
Assignee | ||
Comment 1•14 years ago
|
||
I forgot about this issue, we should really fix this one. If not for 1.4.2 then for a separate mozrunner release right after. Too many people run into this.
Whiteboard: [mozmill-1.4.2?]
Assignee | ||
Comment 2•14 years ago
|
||
quick patch to fix this problem.
Attachment #467323 -
Flags: review?(ctalbert)
Assignee | ||
Comment 3•14 years ago
|
||
Assignee | ||
Updated•14 years ago
|
Summary: mozrunner does not accept full path to binary on OS X → mozrunner does not accept full path to binary on Mac OS X
As much as I hate this behavior and want to see this bug fixed, I can't take it for 1.4.2. I think that ship has sailed. If we do a dot release after 1.4.2 we'll take this as a ride along. (I envision us doing that for the expected event stuff).
Whiteboard: [mozmill-1.4.2?] → [mozmill-1.4.2-]
Comment 5•14 years ago
|
||
Such a change will also break our automation scripts, which will have to be updated. So the impact is a bit broader and I'm not sure how much it will affect other consumers of Mozrunner/Mozmill out there. Sounds good for the next dot release.
Whiteboard: [mozmill-1.4.2-] → [mozmill-1.4.2-][mozmill-1.4.3?]
Assignee | ||
Comment 6•14 years ago
|
||
Okay.
(In reply to comment #5)
> Such a change will also break our automation scripts, which will have to be
> updated. So the impact is a bit broader and I'm not sure how much it will
> affect other consumers of Mozrunner/Mozmill out there. Sounds good for the next
> dot release.
I'm interested in how this breaks current scripts? just specifiying /Firefox.app still works, but /Firefox.app/Contents/MacOS/firefox-bin also works now.
Comment 7•14 years ago
|
||
(In reply to comment #6)
> I'm interested in how this breaks current scripts? just specifiying
> /Firefox.app still works, but /Firefox.app/Contents/MacOS/firefox-bin also
> works now.
Ah ok. So our scripts aren't affected then. Haven't had such a closer look to your patch.
Assignee: nobody → fayearthur+bugs
Status: NEW → ASSIGNED
Updated•14 years ago
|
Whiteboard: [mozmill-1.4.2-][mozmill-1.4.3?] → [mozmill-1.4.2-][mozmill-1.5.1?]
Whiteboard: [mozmill-1.4.2-][mozmill-1.5.1?] → [mozmill-1.4.2-][mozmill-1.5.1+]
Comment on attachment 467323 [details] [diff] [review]
don't add 'Contents/MacOS/x-bin' to binary if they already specify it
Hooray for this patch. r=ctalbert
Attachment #467323 -
Flags: review?(ctalbert) → review+
Reporter | ||
Comment 9•14 years ago
|
||
It looks like this needs to be landed on master too:
http://github.com/mozautomation/mozmill/blob/master/mozrunner/mozrunner/runner.py
Assignee | ||
Comment 10•14 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 11•14 years ago
|
||
It had been landed on hotfix-1.5.1 as:
http://github.com/mozautomation/mozmill/commit/f3f6829552dead9d7935c841e82b5141a00963e9
Checked and I can verify the expected behavior. Thanks!
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•