Bug#836722: [Pkg-javascript-devel] Bug#836722: Bug#836722: Bug#836722: needs yargs as a dependency

2016-11-29 Thread Pirate Praveen
On ചൊവ്വ 29 നവംബര്‍ 2016 01:45 വൈകു, Jonas Smedegaard wrote:
>> My laptop slows to a crawl just before that failure, so I suspect it is 
>> eating up all memory, and I am not in the mood for disabling timeout as 
>> it seems mocha can do.  Any ideas?  Did you succeed a build, Praveen?

Yes, I got it building locally

  64 passing (10s)

I have Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (quad core) with 16 GB RAM.

> Not sure if related to above, but seems the testsuite requires more 
> dependencies - some packaged already, but missing are esfuzz and acorn.  
> Are those in the pipeline to get packaged, or should I perhaps try look 
> into patching testsuite to avoid them for now?

Acorn is ready for upload (ccing Julien who is working on it), I'm not
sure about esfuzz, we can patch it out I think.

Julien, do you need a sponsor, can we upload it?




signature.asc
Description: OpenPGP digital signature


Bug#836722: [Pkg-javascript-devel] Bug#836722: Bug#836722: Bug#836722: needs yargs as a dependency

2016-11-29 Thread Jonas Smedegaard
Quoting Jonas Smedegaard (2016-11-29 08:56:59)
> Quoting Pirate Praveen (2016-11-29 07:55:30)
> > On ചൊവ്വ 29 നവംബര്‍ 2016 11:38 രാവിലെ, Jonas Smedegaard wrote:
> > > How? Please elaborate!
> > > 
> > > Checking now with freshly updated unstable+incoming archives and it 
> > > still fails to satisfy dependencies.
> > 
> > I should have mentioned node-cross-spawn-async 2.2.5-2 (I had drafted
> > such a mail, but gnome-shell broke on my laptop, so missed that detail
> > when typed from mobile)
> > 
> > It just took some time for processing after I uploaded
> > https://tracker.debian.org/news/819919
> 
> Thanks for the details.
> 
> Now (after adding build-dependency on mocha) build fails with these:
> 
>   --- Sourcemaps tests
> ․․․
>   ․
> 
>   62 passing (44s)
>   2 failing
> 
>   1) bin/uglifyjs should produce a functional build when using --self:
>  Error: timeout of 5000ms exceeded
>   at null. (/usr/lib/nodejs/mocha/lib/runnable.js:139:19)
>   at Timer.listOnTimeout (timers.js:92:15)
> 
>   2) spidermonkey export/import sanity test should produce a functional build 
> when using --self with spidermonkey:
>  Error: timeout of 2ms exceeded
>   at null. (/usr/lib/nodejs/mocha/lib/runnable.js:139:19)
>   at Timer.listOnTimeout (timers.js:92:15)
> 
> 
> My laptop slows to a crawl just before that failure, so I suspect it is 
> eating up all memory, and I am not in the mood for disabling timeout as 
> it seems mocha can do.  Any ideas?  Did you succeed a build, Praveen?

Not sure if related to above, but seems the testsuite requires more 
dependencies - some packaged already, but missing are esfuzz and acorn.  
Are those in the pipeline to get packaged, or should I perhaps try look 
into patching testsuite to avoid them for now?


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private



Bug#836722: [Pkg-javascript-devel] Bug#836722: Bug#836722: Bug#836722: needs yargs as a dependency

2016-11-29 Thread Jonas Smedegaard
Quoting Pirate Praveen (2016-11-29 07:55:30)
> On ചൊവ്വ 29 നവംബര്‍ 2016 11:38 രാവിലെ, Jonas Smedegaard wrote:
> > How? Please elaborate!
> > 
> > Checking now with freshly updated unstable+incoming archives and it 
> > still fails to satisfy dependencies.
> 
> I should have mentioned node-cross-spawn-async 2.2.5-2 (I had drafted
> such a mail, but gnome-shell broke on my laptop, so missed that detail
> when typed from mobile)
> 
> It just took some time for processing after I uploaded
> https://tracker.debian.org/news/819919

Thanks for the details.

Now (after adding build-dependency on mocha) build fails with these:

  --- Sourcemaps tests
․․․
  ․

  62 passing (44s)
  2 failing

  1) bin/uglifyjs should produce a functional build when using --self:
 Error: timeout of 5000ms exceeded
  at null. (/usr/lib/nodejs/mocha/lib/runnable.js:139:19)
  at Timer.listOnTimeout (timers.js:92:15)

  2) spidermonkey export/import sanity test should produce a functional build 
when using --self with spidermonkey:
 Error: timeout of 2ms exceeded
  at null. (/usr/lib/nodejs/mocha/lib/runnable.js:139:19)
  at Timer.listOnTimeout (timers.js:92:15)


My laptop slows to a crawl just before that failure, so I suspect it is 
eating up all memory, and I am not in the mood for disabling timeout as 
it seems mocha can do.  Any ideas?  Did you succeed a build, Praveen?


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private



Bug#836722: [Pkg-javascript-devel] Bug#836722: Bug#836722: Bug#836722: needs yargs as a dependency

2016-11-28 Thread Pirate Praveen
On ചൊവ്വ 29 നവംബര്‍ 2016 11:38 രാവിലെ, Jonas Smedegaard wrote:
> How? Please elaborate!
> 
> Checking now with freshly updated unstable+incoming archives and it 
> still fails to satisfy dependencies.

I should have mentioned node-cross-spawn-async 2.2.5-2 (I had drafted
such a mail, but gnome-shell broke on my laptop, so missed that detail
when typed from mobile)

It just took some time for processing after I uploaded
https://tracker.debian.org/news/819919



signature.asc
Description: OpenPGP digital signature