MasterDuke b2gills: none here with master/master/master on Arch Linux. what OS, etc are you using? 00:09
b2gills I wrote a shell script which uses NQP_REVISION and MOAR_REVISION, so it should be the latest pull 00:11
s/pull/bump/ 00:19
Ubuntu 16.04.4 LTS 00:20
MasterDuke hm, i think i once found a problem with an older gcc. what version of that do you have? 00:38
also, i know nothing about nativecall, so i'd say just make an issue and tag nine in it 00:40
b2gills I just blew away /opt/rakudo … and I only have `moar` `nqp` & `nqp-m` in /opt/rakudo/bin. 00:55
So I was apparently using an old revision
Makefile:568: recipe for target 'm-coretest5' failed 00:58
Makefile:620: recipe for target 'm-install' failed
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) 00:59
GNU Make 4.1 01:00
Kaiepi what is Block in nqp? 01:10
timotimo Block, like a class in the hierarchy of Routine and such? 01:11
Kaiepi i'm guessing so 01:12
i can't figure out how to use stuff like nqp::for
timotimo you're writing actual nqp code for the nqp compiler to consume?
Kaiepi though i probably don't really need to use it
no, that's why i say that
also when do i need to use nqp::decont? 01:15
timotimo whenever you get a container in and you want to do stuff with the value in it instead, which is almost always 01:16
in perl6 code, you get deconts code-genned everywhere, and moarvm is good at removing them when they are unnecessary 01:21
because deconting something that isn't a container is a no-op
Kaiepi how do you tell if something has a container? 01:22
timotimo nqp::iscont :) 01:23
m: use nqp; say nqp::iscont(my $foo); say nqp::iscont(my \blop = 1)
camelia 1
Kaiepi ohh
so sigils give vars containers? 01:24
timotimo yup
Kaiepi what about self in class methods?
timotimo iscont is also what different parts of the code decide whether to iterate something or not
not sure, you can try it out :) 01:25
MasterDuke m: use nqp; say nqp::iscont(my $foo := 1);
camelia 0
timotimo right, binding replaces containers
assigning goes into containers 01:26
Kaiepi ohh 01:27
ok now it makes more sense
b2gills make install fails with `./perl6-m tools/build/ /opt/rakudo/share/perl6␤Too few positionals passed; expected 2 arguments but got 1␤ in block <unit> at tools/build/ line 17` 01:37
Geth roast: 432a5531bb | MasterDuke17++ | S02-types/array.t
Test reification (or not) of zen/whatever slices
Zoffix Kaiepi: self is always deconted. One exception (both to self and what iscont gives) is Proxy containers which remain conted (since deconting them would just fetch the value and discard the likely-important Proxy) 01:54
Kaiepi ah
Zoffix huggable: HLL iscont
huggable Zoffix, say $v.VAR ~~ Scalar|Proxy ?? "conted" !! "deconted"
Zoffix ^ the non-NQP way to check if something's is conted
huggable: decont
huggable Zoffix, Article on containers and decont:
Zoffix ^ decent article on containers
"./ undefined reference to `MVM_getrandom'" :S 02:22
timotimo need to again
Zoffix That's on my 32-bit box
Ah. Thanks
Geth nqp/nummy-num: b46ca01ca1 | (Zoffix Znet)++ | t/nqp/115-nums.t
Use original string num in test desc

For easier debugging of failures
nqp/nummy-num: eb50ac8e7e | (Zoffix Znet)++ | t/nqp/115-nums.t
Test we can handle fancy unicode nums
nqp: zoffixznet++ created pull request #438:
Nummy num
nqp/master: 4 commits pushed by (Zoffix Znet)++
Zoffix uhhh.. ."Could not execute (./perl6-m t/spec/S10-packages/precompilation.rakudo.moar): open3: exec of ./perl6-m t/spec/S10-packages/precompilation.rakudo.moar failed: No such file or directory at /home/cpan/perl5/perlbrew/perls/perl-5.24.0/lib/5.24.0/TAP/Parser/Iterator/ line 165." 03:09
oh, nm, I think it was a residual process hanging about after I killed z-script initiated stresstest 03:11
s/think/fairly sure/;
t/02-rakudo/03-cmp-ok.t (Wstat: 512 Tests: 6 Failed: 2) 03:14
Failed tests: 1, 6
Non-zero exit status: 2
t/08-performance/02-qast-rewrites.t (Wstat: 1024 Tests: 5 Failed: 4)
Failed tests: 1-3, 5
Non-zero exit status: 4
t/02-rakudo/repl.t (Wstat: 256 Tests: 42 Failed: 1)
Failed test: 35
Non-zero exit status: 1
sparkling clean the second time... Weird that such a burst of sporadic failures occured :/ 03:17
travis-ci NQP build failed. Zoffix Znet 'Merge pull request #438 from perl6/nummy-num 03:25
Zoffix blows everything out and re-tries the bumps
ZOFFLOP: t/spec/S11-modules/require.t 03:38
ZOFFLOP: t/spec/S07-hyperrace/basics.t t/spec/S10-packages/basic.t 03:42
Geth nqp: aec1b1fd7d | (Zoffix Znet)++ | tools/build/MOAR_REVISION
[MoarVM Bump] Brings 13 commits

MoarVM bump brought: 517e26f Merge pull request #850 from MoarVM/nummy-num c6c0bab Fix denormals and precision issues in num parser c6aba84 don't use %b in format string 7349b42 have to use FSA consistently for this field ... (9 more lines)
¦ nqp: version bump brought these changes:
rakudo: 3d6e25c680 | (Zoffix Znet)++ | tools/build/NQP_REVISION
[NQP Bump] Brings 5 commits

NQP bump brought: aec1b1f [MoarVM Bump] Brings 13 commits 26dae94 Merge pull request #438 from perl6/nummy-num eb50ac8 Test we can handle fancy unicode nums b46ca01 Use original string num in test desc ... (16 more lines)
¦ rakudo: version bump brought these changes:
Zoffix .tell AlexDaniel` the nqp num issues are fully fixed now. I did check on my 32-bit box and both the original failing tests and then new NQP num tests were fine. 04:05
yoleaux Zoffix: I'll pass your message to AlexDaniel`.
stmuk Zoffix++ 06:56
[Tux] Rakudo version 2018.04-17-g3d6e25c68 - MoarVM version 2018.04-32-g517e26f04
csv-ip5xs0.885 - 0.906
csv-ip5xs-208.722 - 9.094
csv-parser37.105 - 38.971
csv-test-xs-200.423 - 0.447
test9.675 - 9.739
test-t2.507 - 2.541
test-t --race1.012 - 1.047
test-t-2044.698 - 45.365
test-t-20 --race15.996 - 16.352
AlexDaniel . 10:36
AlexDaniel` .
yoleaux 01:50Z <Zoffix> AlexDaniel`:
04:05Z <Zoffix> AlexDaniel`: the nqp num issues are fully fixed now. I did check on my 32-bit box and both the original failing tests and then new NQP num tests were fine.
dogbert2_ No such method 'install' for invocant of type 'Str' 10:40
in block <unit> at tools/build/ line 28
wazzup with this?
AlexDaniel Zoffix: but you still think that we should just fudge these tests?
or “fully fixed” means fully fixed and we can ship it? 10:41
jnthn dogbert2_: Thing that was a bug introduced by a commit in Rakudo that was already reverted
*Think 10:46
Zoffix AlexDaniel: 10:52
I don't know. It works and passes stresstests on my 64bit and 32bit boxes. 10:53
But I don't know C so for all I know I wrote a bunch of crap there and it'll explode the second you release a point release :P
Geth nqp: 4d8503982c | (Tobias Leich)++ | tools/build/MOAR_REVISION
Bump moar for inlined fixed sized CArray support
¦ nqp: version bump brought these changes:
Zoffix new num nqp tests pass on win10 too 10:55
Geth rakudo: dbc527d46a | (Tobias Leich)++ | tools/build/NQP_REVISION
Bump nqp/moar for inlined fixed sized CArray support
rakudo: version bump brought these changes:
4c3807c5fb | (Tobias Leich)++ | 4 files

The shape declaration on an attributes was parsed correctly since a while, but now this information is passed to the repr composition. The following is now supported fo CStructs and CPPStructs:
use NativeCall; ... (6 more lines)
rakudo: 7847768cad | (Tobias Leich)++ | src/Perl6/Actions.nqp
Mark the CArray dimension as nut sunk
FROGGS I hope I didn't break anything 10:58
Zoffix AlexDaniel: also, I'm fairly sure the test failures are not a new bug but rather the old bug (failure to choose closest representable num) exposed because our stringification got more precision. Also, I'm not aware of that bug affecting anything on rakudo level. 10:59
AlexDaniel: so yeah, I think the test should be fudged for release and the fix left out of it.
AlexDaniel alright… that kinda makes sense, but then I barely woke up 11:00
Zoffix But other than that yeah, by “fully fixed” I mean the bug is fixed and is covered by tests. 11:03
dogbert2_ jnthn: thx 11:09
travis-ci NQP build failed. Tobias Leich 'Bump moar for inlined fixed sized CArray support' 11:14
FROGGS I guess the just reported failures of t/nqp/106-unicodenames.t and t/nqp/115-nums.t are to be expected on jvm? 11:19
because, what I did can surely have no impact on that 11:20
AlexDaniel that's correct, yes 11:21
but what's exactly failing in 115-nums.t? :)
Zoffix guesses value drift 11:22
FWIW 115-nums.t is a new test file I added last night that covers denormals and value drift in parsing/stringification of nums
FROGGS I see 11:23
Zoffix .tell pmurias I think package-lock.json is something with JS backend innit? Would you know how to fix this Issue? 11:56
yoleaux Zoffix: I'll pass your message to pmurias.
Zoffix Oh, k, "Only users who have been granted access to vulnerability alerts for this repository can see this message." 11:57
Oh, I was wrong, it fails 'cause "not ok 7 - denormal 5e-324 is recognized and is not 0 (Uni)" 12:11
AlexDaniel I guess it's just a matter of using a newer version of that package
Zoffix j: say ೫e-೩೨೪
camelia 5===SORRY!5=== Error while compiling <tmp>
'೫' is not a valid number
at <tmp>:1
------> 3say ೫7⏏5e-೩೨೪
Zoffix m: say ೫e-೩೨೪
camelia 5e-324
Zoffix j: say ೫ 12:12
camelia 5===SORRY!5=== Error while compiling <tmp>
'೫' is not a valid number
at <tmp>:1
------> 3say ೫7⏏5<EOL>
AlexDaniel or maybe not, because there's no point release for that security issue… 12:13
and you'd have to upgrade to a newer major version
Geth nqp: d36869cc27 | (Zoffix Znet)++ | 2 files
Fudge newly-added Unicodey tests on JVM
travis-ci NQP build passed. Zoffix Znet 'Fudge newly-added Unicodey tests on JVM' 12:40
dogbert2_ ZOFFLOP: t/spec/S11-modules/require.t 13:03
when I run the above script separately I sometimes get the following: 13:07
ok 13 - can load Fancy::Utilities at run time 13:08
Use of uninitialized value $repo-id of type Any in string context.
Methods .^name, .perl, .gist, or .say can be used to stringify it to something meaningful.
in any statement_control at blib/Perl6/Grammar.moarvm line 1
if I run it again the message above is gone !
brrt dear #perl6-dev. i would very much appreciate it if someone (who is on linux, or maybe macOS), can checkout the branch `jit-stack-walker` on MoarVM and run a benchmark against master 13:22
for me, spectest passes 13:24
b2gills So my weird problems seem to have disappeared after `git clean -dxf` and removing every remnant from previous builds I could think of (/opt/rakudo/*;~/.perl6/precomp) 14:15
lizmat Files=1239, Tests=76311, 318 wallclock secs (15.71 usr 5.37 sys + 2198.79 cusr 220.31 csys = 2440.18 CPU) 16:01
AlexDaniel Alright, so to me it makes sense just to fudge tests that are not passing on i386 for the point release. This way there's no need to hunt for potential new bugs and no need for moarvm point release. Especially so given that we've not seen any user-facing issues, and that the underlying bug probably existed before 16:17
if anyone disagrees, please speak up :)
and btw, from now on we'll notice this kind of issues on i386 before the release, thanks to El_Che++ 16:22
AlexDaniel deletes all branches that have no commits ahead of master… 16:25
Zoffix +1 16:27
AlexDaniel to be honest I feel like deleting all branches that are 10k+ commits behind 16:29
Zoffix ZOFFLOP: t/spec/S12-class/literal.t 16:32
ZOFFLOP: t/spec/S10-packages/basic.t 16:35
AlexDaniel Alright, this month I'll bother all of you about these stale branches
El_Che AlexDaniel: do the canary work as intended? 16:37
AlexDaniel El_Che: no, but we will see when I'll get the point release preready 16:38
El_Che: I mean, I don't know yet :)
I've been trying to cut a virtual release from master but failed because of issues with File::Which
El_Che AlexDaniel: we know it passes regular releases until 2018.03, so everything failing after that... :) 16:39
AlexDaniel El_Che: but 2018.04 is failing only on i386 right? 16:40
El_Che yes
AlexDaniel so I guess it works then
anyway we'll see tonight
El_Che looking forward to the dot releases. A lot of changes to my pkg repo wainting on a branch: repos for debs and rpms, support for Ubuntu 18.04 amd64/i386, script to set PATH for newbies, support for Linux on Windows for all packages exect alpine (it does not work there yet) instead of only Ubuntu 16:42
now I am reading it, it sounds like a merge nightmare, but travis passes :)
more simple readme as well
Geth nqp/pluggable-spesh: 6eb28874bf | (Jonathan Worthington)++ | src/vm/moar/QAST/QASTOperationsMAST.nqp
Compile MoarVM spesh plugin API ops
nqp/pluggable-spesh: 1d063fd2e5 | (Jonathan Worthington)++ | t/moar/52-pluggable-spesh.t
Add proposed spesh plugin API test
El_Che works JIT on arm? 16:47
jnthn El_Che: No 16:48
Though spesh works, so you still get quickened bytecode, just interpreted still
El_Che so, are arm packages relevant? 16:49
jnthn Why not? Just because you don't get machine code compilation doesn't mean it isn't still overall useful. :)
Zoffix El_Che: 32-bit also doesn't have JIT. It's just slow as hell, but everything still works 16:50
El_Che Zoffix: 32 bit is probably a 64-machine (VM?) with little ram 16:51
arm has slow preocessors and little ram mostly :)
Zoffix ZOFVM: Files=1294, Tests=153324, 152 wallclock secs (21.22 usr 3.51 sys + 3224.19 cusr 175.40 csys = 3424.32 CPU) 16:55
ZOFSPECTESTVM: Files=1239, Tests=76311, 109 wallclock secs (14.99 usr 2.94 sys + 2196.37 cusr 151.92 csys = 2366.22 CPU)
Jit-WalkerVM: Files=1239, Tests=76202, 112 wallclock secs (14.96 usr 3.13 sys + 2251.03 cusr 150.77 csys = 2419.89 CPU)
Jit-WalkerSPECTESTVM: Files=1294, Tests=153215, 152 wallclock secs (21.16 usr 3.67 sys + 3221.38 cusr 170.73 csys = 3416.94 CPU)
Jit-Walker also has a ton of test failuers:
jnthn bbl 16:57
Zoffix System info:
.tell brrt Luke Jit Walker results: 16:58
yoleaux Zoffix: I'll pass your message to brrt.
lizmat m: sub int($a) { $a.Int }; say int(42.3) # probably a case of DIHWIDT 17:28
camelia Cannot invoke this object (REPR: P6int; int)
in block <unit> at <tmp> line 1
Geth rakudo: Kaiepi++ created pull request #1779:
Implement NativeCall CArray.allocate method
Kaiepi note to self: don't put fixes #issuenum in the commit message when you force push all the time in pullreqs 18:00
actually wait, do people push new changes in pullreqs in separate commits here? 18:01
AlexDaniel Kaiepi: I'm +1 on force-fixing commits in pull requests so that the history is clean 18:20
Kaiepi same 18:29
they're useful for pullreqs making huge changes, but that's the only time i can think of where i'd use them 18:32
i just need to fix issues from the pullreq message, not the commit so i don't spam issues
AlexDaniel IMO that's not a big problem… 18:39
lizmat m: sub rand($a) {}; rand(42) # taking the Perl 5 safeties a little bit too far, IMO 20:25
camelia 5===SORRY!5=== Error while compiling <tmp>
Unsupported use of rand(N); in Perl 6 please use N.rand for Num or (^N).pick for Int result
at <tmp>:1
------> 3sub rand($a) {}; rand7⏏5(42) # taking the Perl 5 safeties a li
AlexDaniel lizmat: most of them are this way 20:52
(with false positives getting in your way when you are not even thinking about perl 5) 20:53
timotimo huh, why doesn't it have a check for "is rand from the setting here?"?
probably just an oversight?
lizmat it's in the grammar, can we check for existence of subs there already ? 20:55
would have to add the code gen for it as well then, I think 20:56
timotimo hm, we probably can, but i'm not sure
what do you mean "add the code gen"?
lizmat looks to me the code gen only supports the parameterless case 21:07
timotimo oh, so it's a term?
lizmat yes
timotimo well,t hen
defining a sub doesn't override that, does it?
lizmat m: sub now($a) { $a }; say now(42); # it does 21:08
camelia 42
timotimo aha!
but that at least explains why the code wouldn't find it?
actually, i'm not sure about that
i might need to take something for my headache :|
lizmat get an early night, maybe ? 21:09
timotimo that often leads me to have even worse headaches :)
lizmat this sorta reminds me of needing to have a coffee at 11pm to be able to sleep 21:11
El_Che timotimo: take something and go to bed
lizmat not a healthy lifestyle
El_Che sleeping with headache doesn't work for me eaither
Kaiepi i get cluster headaches and nothing works besides prescriptions 21:20
idk how to help 21:21
timotimo i've not got it nearly as bad as that
AlexDaniel Well, I guess this is relevant:
speaking of which, looking at the graph I think I have a problem of some sort 21:22
some people recommended melatonin pills, but maybe I should go straight to a doctor 21:23
El_Che AlexDaniel: I woudn't self-medicate 21:27
stmuk melatonin is quite effective as a sleep aid sometimes 21:40
tony-o timotimo: check it out 21:56
timotimo oh yeah! that's pretty :)
lizmat tony-o: any chance of a blog post from you re PTS ?
tony-o test = dotted, build dashed
lizmat: yes, i will write one up 21:57
how soon do you need?
lizmat ++tony-o
well, before Monday would be nice, so I can put it in the P6weekly
timotimo what i've been wondering is: if there's one node that has many, many more incoming edges, maybe just mark nodes that would point to it in some way to get the potential mess under control :)
tony-o like Test? 21:58
working on it lizmat
timotimo yeah, like that
tony-o hmm, what would that look like? 21:59
timotimo i mean, with "record" shape you can turn nodes into essentially tables, but i'd assume viewers would get confused
one way i could imagine it would be to color all of those nodes one color, then have a "stand-in" on the side connected to the many-incoming-edges node to show what the color means
this is everything but well-thought-out fwiw
tony-o haha 22:00
yea i'm trying to picture that
timotimo another way would be to have a subgraph with a visible boundary, but i think only dot can handle that
i believe neato would still put stuff in there that doesn't belong, or just generally mess that up :) 22:01
AlexDaniel neato is not going to look good though
not as good as this at least
timotimo you think? i believe neato looks better than dot, often
AlexDaniel ok it may look ok, but it'd be hard to read :) 22:03
timotimo mhm
wait, i think i might have been using dot almost all the time and just got a little confused
tony-o i want to code 'Test' out of the thing anyway 22:04
timotimo mhm
tony-o much cleaner without Test 22:17 22:18
timotimo yes, i like it
tony-o changes to the tree/dot maker are pushed to uxmal 22:19
lizmat # documents to return True 22:23
however, it appears to return Mu
Geth rakudo: 24a907747b | (Elizabeth Mattijsen)++ | src/core/IO/Handle.pm6 is documented as returning True

It was however returning Mu. No tests were hurt during this modification.
nqp/release/2018.04.1: 593121d34d | (Aleks-Daniel Jakimenko-Aleksejev)++ | t/hll/06-sprintf.t
Fudge num precision tests that are failing on i386

There are no known effects of this bug on rakudo level, and the bug itself is fairly old and merely got exposed recently because the stringification got more precision. Proper fix is in the works, but for now these tests can simply be skipped.
MasterDuke would there be any serious downside to building the linux version of rakudo star with `--debug=3`? 23:27
AlexDaniel performance? 23:35
MasterDuke i don't notice that it makes much of a difference
Geth rakudo/release/2018.04.1: 50f15dd88d | (Aleks-Daniel Jakimenko-Aleksejev)++ | tools/build/NQP_REVISION
[NQP Bump] Fudge num precision tests

NQP bump brought:
rakudo/release/2018.04.1: 6c3941e9c7 | (Aleks-Daniel Jakimenko-Aleksejev)++ | 3 files
Log all changes (+ announcement)

Also an entry in the release_guide.pod
MasterDuke turning of optimization definitely does, but not really debug
*off 23:36
AlexDaniel btw everyone is welcome to read what I wrote there ↑ and do corrections 23:37
the actual release will happen many hours later though, releasable is still crunching and I'll have to power-cycle my body for a few hours 23:40
Zoffix: yes? :)
Zoffix Nope nothing. 23:41
Left my pen in here... There it is!
AlexDaniel waves sadly 23:45
Zoffix AlexDaniel: I found something weird 23:57
c: 2017.12,HEAD say 1e10000; say now - BEGIN now
committable6 Zoffix, ¦2017.12: «Inf␤0.0179175␤» ¦HEAD(24a9077): «Inf␤0.0138853␤»
Zoffix c: 2017.12,HEAD say 1e10000000; say now - BEGIN now
committable6 Zoffix, ¦2017.12: «Inf␤0.05390729␤» ¦HEAD(24a9077): ««timed out after 10 seconds» «exit signal = SIGHUP (1)»»
Zoffix c: 2017.12,HEAD say 1e100000; say now - BEGIN now
committable6 Zoffix, ¦2017.12: «Inf␤0.0318292␤» ¦HEAD(24a9077): «Inf␤0.03483203␤»
Zoffix c: 2017.12,HEAD say 1e1000000; say now - BEGIN now
committable6 Zoffix, ¦2017.12: «Inf␤0.048287␤» ¦HEAD(24a9077): «Inf␤0.0294888␤»
Zoffix c: 2017.12,HEAD say 1e10000000; say now - BEGIN now 23:58
committable6 Zoffix, ¦2017.12: «Inf␤0.0660409␤» ¦HEAD(24a9077): ««timed out after 10 seconds» «exit signal = SIGHUP (1)»»
Zoffix aw, shit, I know what it's doing.
it's making a bigint with 10000000 zeros