Re: not enough memory

[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 day or so ago I got:
>
> "MoarVM panic: Heap corruption detected: pointer 0x7f0fe9a16410 to past
> fromspace"
> https://travis-ci.org/spitsh/spitsh/builds/247357557#L1355
>
> Are you also using a recent rakudo?

Not really.

This is Rakudo version 2017.06 built on MoarVM version 2017.06
implementing Perl 6.c.


>
> LL
>
>
> On Thu, Jun 29, 2017 at 4:37 PM Gabor Szabo  wrote:
>>
>> 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 it worked.
>>
>> The second command kept the same error message.
>>
>> This machine had 1 Gb memory.
>>
>> After adding another Gb the second command worked as well.
>>
>> Gabor

Re: not enough memory

[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 past
fromspace"
https://travis-ci.org/spitsh/spitsh/builds/247357557#L1355

Are you also using a recent rakudo?

LL


On Thu, Jun 29, 2017 at 4:37 PM Gabor Szabo  wrote:

> 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 it worked.
>
> The second command kept the same error message.
>
> This machine had 1 Gb memory.
>
> After adding another Gb the second command worked as well.
>
> Gabor
>

Re: Version of a Module

[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 withouth having this 
suffix in it?



Am 28.06.2017 um 14:16 schrieb Simon Proctor:


See I'm using mi6 to generate my META6.json file from the report and 
it picks the version up from the module file. Other options like that 
seem sensible to me.


Simon


On Wed, 28 Jun 2017, 13:01 Martin Barth, > wrote:


Hello,

but your approach means you have to state the version in the
META6.json AND in the Module.pm6 file again. This would be the
similar to having $VERSION in perl5. Shouldnt there be a simpler way?


Am 28.06.2017 um 08:45 schrieb Fernando Santagata:


Hi Martin,

This works for me:

File mytest.pm6

use v6;
unit module mytest:ver<0.0.1>;

sub myver is export
{
  mytest.^ver;
}

File mytest.p6

#!/usr/bin/env perl6
use lib '.';
use mytest;

say myver;

Console output:

$./mytest.p6
v0.0.1

I this what you meant?

On Tue, Jun 27, 2017 at 10:37 PM, Martin Barth > wrote:

Hello everyone,

I wanted to repeat the question that I asked today on #perl6.
I am looking for a way to retrieve the version of a
Perl6-Module from within the module itself.

 there is often a our $VERSION in perl5 modules. is
this still idiomatic/a good way to go in perl6
 i think the version is meant to be part of the
meta info and such?
 but that means the module itself does not know about
its version, just e.g. zef does?
 i'm convinced there ought to be a way to get the
full meta info from whatever installation your script was
grabbed from
 but i don't know what or how




-- 
Fernando Santagata

not enough memory

[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 it worked.

The second command kept the same error message.

This machine had 1 Gb memory.

After adding another Gb the second command worked as well.

Gabor