[Pkg-javascript-devel] Bug#675856: [PATCH 5/5] update changelog

[shawn]

On Sun, 2012-06-03 at 23:25 +0200, Jérémy Lal wrote: 
> Apparently you did not read my reply to #675856 ?
> 
> It's nice of you to propose patches but it's even better
> to consider my opinion about that.
> 
> Jérémy.
> 
Nope, did not get that yet

anyways, of the part of the test suite that has ran, I got one failure
so far

Running C++ lint check...
Traceback (most recent call last):
  File "/mnt/source/v8/tools/presubmit.py", line 388, in <module>
    sys.exit(Main())
  File "/mnt/source/v8/tools/presubmit.py", line 378, in Main
    success = CppLintProcessor().Run(workspace) and success
  File "/mnt/source/v8/tools/presubmit.py", line 189, in Run
    if not self.ProcessFiles(all_files, path):
  File "/mnt/source/v8/tools/presubmit.py", line 249, in ProcessFiles
    results = pool.map_async(CppLintWorker, commands).get(999999)
  File "/usr/lib/python2.7/multiprocessing/pool.py", line 528, in get
    raise self._value
UnboundLocalError: local variable 'process' referenced before assignment
=== release packed-elements
===                                                
Path: mjsunit/packed-elements
/mnt/source/v8/test/mjsunit/mjsunit.js:166: Failure: expected <true>
found <false>
    throw new MjsUnitAssertionError(message);
          ^
Error
    at new MjsUnitAssertionError
(/mnt/source/v8/test/mjsunit/mjsunit.js:31:16)
    at fail (/mnt/source/v8/test/mjsunit/mjsunit.js:166:11)
    at assertEquals (/mnt/source/v8/test/mjsunit/mjsunit.js:237:7)
    at assertTrue (/mnt/source/v8/test/mjsunit/mjsunit.js:275:5)
    at test1 (/mnt/source/v8/test/mjsunit/packed-elements.js:35:3)
    at test_with_optimization
(/mnt/source/v8/test/mjsunit/packed-elements.js:99:32)
    at /mnt/source/v8/test/mjsunit/packed-elements.js:105:3
Command: /mnt/source/v8/out/arm.release/d8 --nobreak-on-abort
--allow-natives-syntax --smi-only-arrays
--packed-arrays /mnt/source/v8/test/mjsunit/mjsunit.js /mnt/source/v8/test/mjsunit/packed-elements.js --test


I wanted a newer libv8 *right now* so i could fix chromium 20 on armel.
see bug 674728, were i got 18 to build (but with memory alignment
issues)
-- 
-Shawn Landden