not enough memory

2017-06-29 Thread Gabor Szabo
hi, I've got this "not enough memory" twice today while trying to upgrade some packages using zef. Once when I ran 'zef upgrade zef' and then again when I ran 'zef --debug upgrade Bailador'. In both cases the error was shown during the running of the tests. After running the first command again

Re: not enough memory

2017-06-29 Thread Lloyd Fournier
I'm not sure if it's related but I've been getting a few weird memory related issues with HEAD and zef. e.g my travis build just segfaulted: https://travis-ci.org/spitsh/spitsh/builds/248242106#L1355 And a day or so ago I got: "MoarVM panic: Heap corruption detected: pointer 0x7f0fe9a16410 to

Re: not enough memory

2017-06-29 Thread Gabor Szabo
On Thu, Jun 29, 2017 at 11:43 AM, Lloyd Fournier wrote: > I'm not sure if it's related but I've been getting a few weird memory > related issues with HEAD and zef. e.g my travis build just segfaulted: > > https://travis-ci.org/spitsh/spitsh/builds/248242106#L1355 > > And a

Re: Version of a Module

2017-06-29 Thread Martin Barth
yap, when mi6 updates your META6.json this makes sense to me as well. This leads me to another question Can zef/perl6 handle differend modules version based on the suffix ':ve<0.0.1>' or based on the META6.json. I mean, could there be 2 scripts each using a different version of my module