|cfx testall| fails with "could not find compatible GRE" on Mac OS X

RESOLVED WONTFIX

Status

Add-on SDK
General
RESOLVED WONTFIX
8 years ago
7 years ago

People

(Reporter: myk, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
On my Mac OS X 10.6.3 system, |cfx testall| hangs with the message "could not find compatible GRE between version 1.9.1.0 and 1.9.3.*," perhaps because I don't have XULRunner installed, even though I do have Firefox installed, since |cfx testall -a firefox| works fine.

Given that many more developers are likely to have Firefox installed than XULRunner, it seems like the generic |cfx testall| command should work even if you don't have XULRunner installed.

Comment 1

8 years ago
Weird, this actually shouldn't be happening--by default, cfx first tries to find XULRunner at a default location on your system, then tries Firefox and runs it in XULRunner mode if that's not available.

I'm wondering if this is actually due to this change:

  http://hg.mozilla.org/labs/jetpack-sdk/diff/c18a103886e3/python-lib/cuddlefish/runner.py

Do you have a file existing at /usr/bin/xulrunner?

Comment 2

8 years ago
Er wait, didn't realize you're having this problem on OS X. In that case, it may be due to bug 555469.

The weird thing is that my OS X machine doesn't currently have XULRunner on it, and 'cfx testall' works fine. Do you have some kind of file at /Library/Frameworks/XUL.framework/xulrunner-bin?
(Reporter)

Comment 3

8 years ago
(In reply to comment #2)
> Er wait, didn't realize you're having this problem on OS X. In that case, it
> may be due to bug 555469.
> 
> The weird thing is that my OS X machine doesn't currently have XULRunner on it,
> and 'cfx testall' works fine. Do you have some kind of file at
> /Library/Frameworks/XUL.framework/xulrunner-bin?

Erm, yes, so I guess I do have XULRunner:

(jetpack-sdk)host-5-12:jetpack-sdk myk$ /Library/Frameworks/XUL.framework/xulrunner-bin --version
Mozilla XULRunner 1.9.1b3 - 20090327033448

I guess I just have a too-old version of it?

Comment 4

8 years ago
:(

Perhaps we should have cfx print out the binary that it's using if the '-v' argument is passed in, to make debugging this stuff easier. Right now I don't think there's any easy way to actually figure out what it's running when it auto-detects the binary.
(Reporter)

Comment 5

8 years ago
Either that or fall back to a Firefox binary if the XULRunner binary is too old.  Or do both, in which case the process would look something like:

 $ cfx testall
 Running tests on XULRunner...
 XULRunner binary located, but it's too old (1.9.1b3; need 1.9.1.0 to 1.9.3.*).
 Running tests on Firefox instead...
(Reporter)

Comment 6

7 years ago
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product.

To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
(Reporter)

Comment 7

7 years ago
This doesn't particularly matter now that XULRunner is no longer the default application.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.