Closed Bug 840625 Opened 11 years ago Closed 11 years ago

install node 0.8.18 on the ubuntu test slaves

Categories

(Release Engineering :: General, defect)

All
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jmaher, Assigned: rail)

References

(Blocks 1 open bug)

Details

Attachments

(2 files, 1 obsolete file)

We have node 0.6.12 installed on the ubuntu test slaves, but this doesn't work for the xpcshell test_spdy.js testcase.  

I found the source for node:
http://blog.nodejs.org/2012/01/23/node-v0-7-1/

then ran './configure;make;make install' and had /usr/local/bin/node.

Once this is installed, we need to make sure we are running with MOZ_NODE_PATH=/usr/local/bin/node and the xpcshell tests will pass!
Looking at nodejs.org, it looks like 0.7.1 is "unstable", which doesnt sound like something we'd want to use in production. 

2012.01.23, Version 0.7.1 (unstable)

On http://nodejs.org/download/, they have 0.8.19 as the "current" (Stable?) version. 


Do the tests pass if we use 0.8.19?
yes, we should use 0.8.19 as that works just fine.
Assignee: nobody → rail
Summary: install node 0.7.1 on the ubuntu test slaves → install node 0.8.19 on the ubuntu test slaves
0.8.x requires a newer version of v8 library which is not available for 12.04. May need to build that as well.
FTR, the new package installs node as /usr/bin/nodejs. nodejs-legacy package creates /usr/bin/node -> nodejs simlink.

A scenario to avoid the "legacy" package:

* add reverse symlink on Fedora slaves: ln -s node /usr/bin/nodejs
* deploy the package on Ubuntu slaves. It's safe to deploy the new package even though it removes /usr/bin/node, because UBUNTU SPDY tests aren't enabled for production branches.
* update http://hg.mozilla.org/build/buildbotcustom/file/84568b554fbc/env.py#l80 to point to /usr/bin/nodejs


Another scenario would be:

* Use ensure => "$current_version" for nodejs
* upload the new package
* replace nodejs with nodejs-legacy and ensure=>latest
* enjoy
Attached patch nodejs-legacy (obsolete) — Splinter Review
Attachment #715559 - Flags: review?(dustin)
Comment on attachment 715559 [details] [diff] [review]
nodejs-legacy

I'm confused why nodejs-legacy is a newer version than nodejs?  And why are we using ensure => latest for something we want a specific version of?  It'd be great to have some comments here as to why -legacy.
Attachment #715559 - Flags: review?(dustin) → review-
Attached patch Add commentsSplinter Review
Attachment #715559 - Attachment is obsolete: true
Attachment #715588 - Flags: review?(dustin)
Attachment #715588 - Flags: review?(dustin) → review+
Attached patch update repo-flagSplinter Review
r=dustin on IRC
http://hg.mozilla.org/build/puppet/rev/50f4cb3071e1
Attachment #715627 - Flags: review+
Attachment #715627 - Flags: checked-in+
We ended up with 0.8.18~dfsg1-1mozilla1 (since 0.8.19 hasn't been packaged yet upstream)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Summary: install node 0.8.19 on the ubuntu test slaves → install node 0.8.18 on the ubuntu test slaves
It looks like this might have caused a resurgence in bug 749890
Blocks: 749890
(In reply to Nick Hurley [:hurley] from comment #11)
> It looks like this might have caused a resurgence in bug 749890

Do you have any link to an orange test handy?

It looks like the oranges I'm seeing on m-i are caused by https://bugzilla.mozilla.org/show_bug.cgi?id=771578#c6
ccing jmaher who may have some ideas.
Doesn't Cedar last week know? It's one slave failing the exact same way we did on every slave before this bug landed.
Bah, tst-linux32-ec2-334 just got nodejs upgraded... :/

Start-Date: 2013-02-20  19:34:29
Commandline: /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install nodejs-legacy
Install: libv8-3.11.10:i386 (3.11.10.25-1mozilla1, automatic), nodejs-legacy:i386 (0.8.18~dfsg1-1mozilla1)
Upgrade: nodejs:i386 (0.6.12~dfsg1-1ubuntu1, 0.8.18~dfsg1-1mozilla1)
End-Date: 2013-02-20  19:34:36

/me blames himself and bug 839562
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: