Closed Bug 511911 Opened 15 years ago Closed 15 years ago

Need to Update jscoverage tool to revision 453

Categories

(Release Engineering :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: murali, Assigned: armenzg)

Details

We have found a bug in the way jscoverage tool is collecting coverage numbers and got a fix landed in the jscoverage tool. This requires the version update for jscoverage on RE systems Can you please check out the latest SVN revision [ 453 ] for jscoverage , compile and update build system. I have tested and complied the latest revision on CentOS system and it works.
OS: Windows NT → Linux
We would like to deploy it early in this coming week
Assignee: nobody → armenzg
Status: NEW → ASSIGNED
Please provide update on the status
(In reply to comment #2) > Please provide update on the status We are working on it and found that the latest revision is 456 (http://svn.siliconforks.com/jscoverage/trunk/) instead of 453. Which revision would you prefer? I will try to compile myself but I would like to know if you already have a specific set of instructions that you follow. Sorry for the delay with this
I have worked with 453 and found it to be good. I have not tried 456. Can you please build on Version 453 for now. Thanks Murali
cvs commit -m "bug 511911: Need to Update jscoverage tool to revision 453 - update jscoverage and jscoverage-server binaries to new revision." \cvs commit: Examining . Checking in jscoverage; /mofo/puppet-files/centos5/usr/local/bin/jscoverage,v <-- jscoverage new revision: 1.2; previous revision: 1.1 done Checking in jscoverage-server; /mofo/puppet-files/centos5/usr/local/bin/jscoverage-server,v <-- jscoverage-server new revision: 1.2; previous revision: 1.1 done
For reference: 942769e2146c3c9c4417ebed656eaa89 /usr/local/bin/jscoverage 25606dab9bfaf619a7718f36265dfe6a /usr/local/bin/jscoverage-server I have checked few slaves and they have the same md5sum.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.