On 25/11/2011 17:56, Jonas Smedegaard wrote:
> On 11-11-25 at 10:06am, Jonas Smedegaard wrote:
>> On 11-11-24 at 12:06am, Jérémy Lal wrote:
>>> libv8 126.96.36.199-1 is ready to be reviewed and uploaded to unstable.
>>> The big change is the move to gyp-based building (but makefiles are
>>> generated by upstream instead of regenerating them).
>>> libv8 188.8.131.52-1 could also be uploaded to experimental, it's easier
>>> to review because the changes since 3.5 are very straightforward.
>>> nodejs 0.6.2, depends on libv8 184.108.40.206, is buildable.
>>> It still needs debian/copyright work, and nodejs-dbg binary package is
>>> broken (and removed from debian/control.in for now).
>>> The big deception is 0.6 branch is still using waf as build system.
>>> Even more messy is usage of custom versions of ev and cares in the new
>>> uv backend.
>>> It might be impossible for now to make nodejs use the libev4 and
>>> libc-ares packages, so uv backend uses its custom versions.
>>> There are some test failures, but it looks good nonetheless.
>>> I'd appreciate reviews, advices about those packages.
>> Thanks for the summary -and for your patience.
>> It looks sensible to me - I am giving it a try now...!
> === release regress-funcaller ===
> Path: mjsunit/compiler/regress-funcaller
> Command: /tmp/buildd/libv8-220.127.116.11/out/x64.release/d8 --stress-opt
> --always-opt /tmp/buildd/libv8-18.104.22.168/test/mjsunit/mjsunit.js
> /tmp/buildd/libv8-22.214.171.124/test/mjsunit/compiler/regress-funcaller.js --test
> --- TIMEOUT ---
> [16:53|% 100|+ 3830|- 1]: Done
>>>> running tests for x64.release
> make: *** [x64.release.check] Error 1
> make: Leaving directory `/tmp/buildd/libv8-126.96.36.199'
> make: *** [debian/stamp-makefile-check] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> E: Failed autobuilding of package
I forgot to apply --timeout=120 parameter needed when running tests on some
Pushed to master & master-experimental.