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)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jmaher, Assigned: rail)
References
(Blocks 1 open bug)
Details
Attachments
(2 files, 1 obsolete file)
818 bytes,
patch
|
dustin
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
1.00 KB,
patch
|
rail
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
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!
Comment 1•11 years ago
|
||
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?
Reporter | ||
Comment 2•11 years ago
|
||
yes, we should use 0.8.19 as that works just fine.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → rail
Assignee | ||
Updated•11 years ago
|
Summary: install node 0.7.1 on the ubuntu test slaves → install node 0.8.19 on the ubuntu test slaves
Assignee | ||
Comment 3•11 years ago
|
||
0.8.x requires a newer version of v8 library which is not available for 12.04. May need to build that as well.
Assignee | ||
Comment 4•11 years ago
|
||
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
Assignee | ||
Comment 5•11 years ago
|
||
Attachment #715559 -
Flags: review?(dustin)
Comment 6•11 years ago
|
||
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-
Assignee | ||
Comment 7•11 years ago
|
||
Attachment #715559 -
Attachment is obsolete: true
Attachment #715588 -
Flags: review?(dustin)
Updated•11 years ago
|
Attachment #715588 -
Flags: review?(dustin) → review+
Assignee | ||
Comment 8•11 years ago
|
||
Comment on attachment 715588 [details] [diff] [review] Add comments http://hg.mozilla.org/build/puppet/rev/efa81aeb1669
Attachment #715588 -
Flags: checked-in+
Assignee | ||
Comment 9•11 years ago
|
||
r=dustin on IRC http://hg.mozilla.org/build/puppet/rev/50f4cb3071e1
Attachment #715627 -
Flags: review+
Attachment #715627 -
Flags: checked-in+
Assignee | ||
Comment 10•11 years ago
|
||
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
Comment 11•11 years ago
|
||
It looks like this might have caused a resurgence in bug 749890
Blocks: 749890
Assignee | ||
Comment 12•11 years ago
|
||
(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
Comment 13•11 years ago
|
||
https://tbpl.mozilla.org/php/getParsedLog.php?id=19925084&tree=Mozilla-Inbound and the misstar from bug 749890 comment 231, https://tbpl.mozilla.org/php/getParsedLog.php?id=19926864&tree=Try, which are both on tst-linux32-ec2-334
Assignee | ||
Comment 14•11 years ago
|
||
ccing jmaher who may have some ideas.
Comment 15•11 years ago
|
||
Doesn't Cedar last week know? It's one slave failing the exact same way we did on every slave before this bug landed.
Assignee | ||
Comment 16•11 years ago
|
||
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
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•