Opened on 04/10/2014 at 02:50:59 PM

Closed on 04/15/2014 at 09:25:44 PM

#298 closed change (fixed)

JSHydra is unable to download a SpiderMonkey build

Reported by: trev Assignee: trev
Priority: P3 Milestone:
Module: Automation Keywords:
Cc: Blocked By:
Blocking: Platform:
Ready: yes Confidential: no
Tester: Verified working: no
Review URL(s):



Currently JSHydra will try to download a SpiderMonkey build from - these builds are gone however. We currently cannot switch to newer releases because of parser changes that will rewrite loops into let statements.

What to change

It seems that we should go with a random nightly instead of using release candidates, nightlies stay on the download servers forever.

Attachments (0)

Change History (8)

comment:1 Changed on 04/10/2014 at 02:53:26 PM by trev

  • Review URL(s) modified (diff)
  • Status changed from new to reviewing

comment:2 Changed on 04/11/2014 at 01:20:34 PM by trev

  • Resolution set to fixed
  • Status changed from reviewing to closed

comment:3 Changed on 04/12/2014 at 07:37:27 AM by trev

  • Resolution fixed deleted
  • Status changed from closed to reopened

As noted in, we no longer need to stay with outdated SpiderMonkey builds. Reopening, we should be using something more current then.

comment:4 Changed on 04/12/2014 at 01:26:22 PM by tschuster

I would suggest we use the latest stable release, based on Fx 24. Sadly at least right now we can't directly use one of the offical releases of mozjs, because those don't actually include a shell.

For now we could use, but I am not sure how long that URL stays alive.

comment:5 Changed on 04/12/2014 at 06:36:09 PM by trev

That's the problem, this URL won't stay alive. We had to change URLs several times already, I'd rather stop doing this. It's like this:

It seems that we have to use a nightly, that's the only reliable option - we should change the URL when we want it, not when we have to because the build disappeared. I wouldn't go with latest-*, it should be a specific build where we know that everything works. The question is merely whether we go with trunk (31.0a1) or current release (28.0), I don't really have a preference here as long as they produce the same results.

comment:6 Changed on 04/14/2014 at 04:53:52 PM by tschuster

The best thing that I have been able to find so far is Aurora builds. I couldn't find anything like latest-release or beta or even esr.

comment:7 Changed on 04/15/2014 at 08:09:59 AM by trev

  • Review URL(s) modified (diff)
  • Status changed from reopened to reviewing

You are right, it seems that nightly builds for release branches are no longer being created (other than debug builds which we shouldn't use). So we basically have the choice between ESR, trunk and Aurora. I tested the ESR build from and it produces exactly the same results, so I guess we can go with it.

Concerning the issue mentioned in the issue description that prevents us from using newer SpiderMonkey builds - turns out I fixed it a year ago. So it's not exactly surprising newer builds work correctly.

comment:8 Changed on 04/15/2014 at 09:25:44 PM by trev

  • Resolution set to fixed
  • Status changed from reviewing to closed

Add Comment

Modify Ticket

Change Properties
as closed .
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from trev.
Note: See TracTickets for help on using tickets.