Zoffix PR to fix Fix RT#128019: LTA warning on smartmatch against S/// github.com/rakudo/rakudo/pull/789 00:17
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=128019
MasterDuke .tell timotimo valgrind output when my modified htmlify.p6 segfaulted, gist.github.com/MasterDuke17/c10c8...a20beedad4 00:59
yoleaux2 MasterDuke: I'll pass your message to timotimo.
timotimo sorry, but that's pretty much useless without the line number information :( 01:01
yoleaux2 00:59Z <MasterDuke> timotimo: valgrind output when my modified htmlify.p6 segfaulted, gist.github.com/MasterDuke17/c10c8...a20beedad4
timotimo you didn't build it with --debug=3 in your moarvm's Configure.pl?
MasterDuke no, but i'll do that now 01:04
just moarvm, not nqp or rakudo? 01:05
timotimo just moarvm 01:06
rakudo only has a tiny amount of C code
what we need is the DWARF debug symbols in the libmoar.so file to be available
MasterDuke restarted after adding --debug=3 to moarvm, but this'll take a while 01:09
timotimo probably 01:10
thanks a lot for the help!
MasterDuke likewise
timotimo i'll probably go to bed quite soon, so i'll rely on yoleaux to relay the paste to me 01:11
but it's strange that it's not giving any errors before the segfault happens 01:12
hm, actually, valgrind doesn't know anything about our fixed size allocator, so it can't figure out when we're overstepping boundaries
can you reset the run again and do the following change:
MasterDuke there are still a bunch of these: Syscall param write(buf) points to uninitialised byte(s) 01:13
you can see one here, gist.github.com/MasterDuke17/05151...b11d0f8db2
timotimo that's also strange
find fixedsizealloc.c and change the define for FSA_SIZE_DEBUG to 1 01:14
that'll make things a bit slower still, but it may find bogus writes 01:15
MasterDuke restarted 01:18
timotimo thank you kindly
i'm hopeful it'll help
i'll probably not be able to find the cause (or fix) for the uninitialized bytes 01:19
MasterDuke off with your head! 01:20
in case you wanted the valgrind output with FSA_SIZE_DEBUG=1 for one of them anyway ... gist.github.com/MasterDuke17/13e82...27445eb575 01:23
.tell timotimo ah-ha, here's a segfault, gist.github.com/MasterDuke17/56d63...03c8b29f13 01:27
yoleaux2 MasterDuke: I'll pass your message to timotimo.
timotimo wrong link? i don't see the segfault 01:28
yoleaux2 01:27Z <MasterDuke> timotimo: ah-ha, here's a segfault, gist.github.com/MasterDuke17/56d63...03c8b29f13
MasterDuke oops, gist.github.com/MasterDuke17/470aa...933d9e8d02 01:29
timotimo cool, can you also give me the core dump? 01:30
MasterDuke the vgcore.<number> file? 01:31
timotimo probably
that might allow me to see what values are where
how big is it? 01:32
MasterDuke 787mb
sorry, wrong one, it's actually only 620mb
timotimo OK, i guess that's fair 01:33
line 2008 seems to be in getattrs_o, is that the same on your machine?
interp.c, i mean
MasterDuke -1, &GET_REG(cur_op, 0), MVM_reg_obj); 01:34
timotimo i wonder if the read in GET_REG did that?
MasterDuke i hope that's a rhetorical question, because i'm not going to be any help answering 01:36
timotimo :) 01:40
maybe the core dump lets me figure that out
MasterDuke i don't mind uploading it somewhere if you want to download it 01:41
dalek kudo/nom: 5eba2cd | (Zoffix Znet)++ | / (3 files):
Make cmp-ok take user-defined operators as Str b2gills++

This rescinds the claim made in commit 102b0eade9093a38d4bb526014d860e87c3e7797 that Str comparator for custom ops is not supported. b2gills++ shown a way to support that, which is what this commit implements.
02:11
kudo/nom: a6e0cc2 | lizmat++ | / (3 files):
Merge pull request #788 from zoffixznet/cmp-ok-custom-ops-via-str

Make cmp-ok take user-defined operators as Str b2gills++
kudo/nom: be210fb | (Zoffix Znet)++ | src/Perl6/Actions.nqp:
Fix RT#128019: LTA warning on smartmatch against S///
02:12
kudo/nom: 449a2e7 | lizmat++ | src/Perl6/Actions.nqp:
Merge pull request #789 from zoffixznet/fix-RT128019-warning-on-S-replacement

Fix RT#128019: LTA warning on smartmatch against S///
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=128019
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=128019
MasterDuke lizmat: what's your opinion on the state of rakudo PR #773? anything i should add or change? 02:16
dalek kudo/nom: 7036028 | (Daniel Green)++ | src/core/IO/ (3 files):
Implement RT #125489. Adds a mode method to IO::[Path.Handle,Special] that returns the file permissions as either an Int or Str.
02:41
kudo/nom: 9bfd0c8 | (Daniel Green)++ | / (2 files):
Move allomorphs.pm before IO so IO::Path.mode can return an IntStr
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=125489
kudo/nom: 3ab95a1 | (Daniel Green)++ | src/core/IO/ (2 files):
Fix signatures for IO::Handle and IO::Special
kudo/nom: ed1b2e4 | (Daniel Green)++ | src/core/IO/Path.pm:
Convert STATEMENT_LIST to nqp::stmts
rakudo/nom: 880f5cb | lizmat++ | / (4 files):
MasterDuke ha, guess it was good enough 02:45
lizmat: thanks 02:47
lizmat MasterDuke: no, thank you! 02:48
:-)
bartolin good morning, #perl6-dev 07:09
it is my sad duty to report some new spectest breakage on rakudo-j. today's spectest run had nearly 7400 failed tests (though most of them are due to aborted test files) 07:10
I looked at two or three examples and all failed with 'getextype needs an object with VMException representation'
m: say <a b>.[lazy ^3] # dies on r-j
camelia rakudo-moar 880f5c: OUTPUTĀ«(a b)ā¤Ā»
bartolin on a more positive note: most failures seem to be related to e5443765d4. I'm currently running a spectest with that commit reverted and it looks ok-ish so far. so at least it seems to be an isolated problem 07:11
ah, also the latest merge missed an adjustment for Makefile-JVM -- cmp. PR 790 07:13
FROGGS o/ 07:19
bartolin \o 07:20
dalek ast: 111b906 | usev6++ | S02-literals/adverbs.t:
Fudge test for RT #128306 on rakudo-j
07:21
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=128306
[Tux] This is Rakudo version 2016.05-177-g880f5cb built on MoarVM version 2016.05-37-ga126e0f 07:59
test 16.472
test-t 9.476
csv-parser 22.439
RabidGravy I keep expecting to see it leap up to 11 or something 08:04
[Tux] are you a pessimist? 09:40
dalek kudo/nom: 6d055dd | bartolin++ | tools/build/Makefile-JVM.in:
Move allomorphs.pm before IO on JVM as well

this mirrors the change from 9bfd0c8dc6 so that rakudo-j compiles
10:11
kudo/nom: f192415 | jnthn++ | tools/build/Makefile-JVM.in:
Merge pull request #790 from usev6/patch-1

Move allomorphs.pm before IO on JVM as well
stmuk s/pessimist/realist 10:24
jnthn
.oO( implementer sadist :P )
10:32
MasterDuke whoops, my bad about 6d055dd. i usually spectest with rakudo-j also, guess i missed that one
and 111b906! i'm on a roll in the wrong direction 10:33
bartolin MasterDuke: np, it was easy to fix :-) 10:43
jnthn Zoffix: MoarVM release is done: www.moarvm.org/releases/MoarVM-2016.06.tar.gz 10:47
Zoffix: Happy releasing!
bartolin another thing that changed on rakudo-j: I get an error message 'Unhandled exception; category = 65536' instead of X::ControlFlow::Return 11:06
m: return
camelia rakudo-moar f19241: OUTPUTĀ«Attempt to return outside of any Routineā¤ in block <unit> at <tmp> line 1ā¤ā¤Ā»
Zoffix RabidGravy, why would it leap? It didn't get to 9.476 for no reason. 11:37
stmuk whats the rough status of JVM? (I lose track) Does it print hello world but fail with a lot of modules? Or is a build likely to be less successful than that even? 12:04
Zoffix Are we doing Star release for 2016.06? 12:30
stmuk good question .. previously I had thought every 3 months might be the sweet spot but the performance implications of this release are tempting 12:43
or maybe wait a month for even more? 12:44
I will probably do some star updates either way 12:45
Zoffix every 3 months sounds alright
stmuk star 2016-07 sounds good for YAPC::EU the following month 12:50
bartolin stmuk: rakudo-j compiles but installing fails due to a precomp related error. also quite some tests are fudged due to two or three annoying bugs, which might be GLR related. (psch++ has worked on that and knows more details)
apart from that my daily spectests where more or less ok during the last month 12:51
stmuk bartolin: thanks! that's useful to know ... a star jvm one day!
bartolin also, as mentioned earlier today there are some new failures after yesterdays merge from jnthn++ 12:52
btw, nine++ and psch++ have worked on the precomp problem, but it proved to be hairy 12:53
stmuk "Annoy /r/golang in one sentence. (self.golang)" 13:00
I hope this meme doesn't reach /r/perl6 :)
psch "is perl6 production ready" 13:48
probably wins
anyway, yeah, r-j is really weirdly broken, and i wish i could verify that the potential solution i have figured out is the actual solution 13:49
because the potential solution is terrible to implement and involves a lot of fiddling with things through nearly the whole nqp-j stack
and even worse, not getting it to work wouldn't prove it the wrong solution /o\ 13:50
mst you're supposed to wait for a meme to practice annoying people? I've been doing it wrong all these years ... 13:51
psch basically, the problem we're having is that somewhere in the depths of loading-precomp-files we lose a coderef
eh, not quite, we discover during loading-precomp-files that we *already* lost a coderef
so we end up trying to set lex values on null, and that doesn't work 13:52
Zoffix Heh: "===SORRY!=== No JVM (java executable) in path; cannot continue" 13:53
psch okay, that's new :)
Zoffix wonders what Debian package is need to get jvm 13:54
psch openjdk-$something should work 13:55
Zoffix Thanks
TimToady mst: you don't really have to wait; it's sufficient to hold a meme or two in reserve to club people with after you've annoyed them for other reasons 13:58
psch Zoffix: fwiw, with jdk8 you get a few more passing unicode tests, but since we do support jdk7 they shouldn't be un-todo'd 14:01
Zoffix doesn't have 8 in repos
psch we do need jdk7, in any case, 'cause invokedynamic 14:02
MasterDuke TimToady: what's your opinion on irclog.perlgeek.de/perl6/2016-06-17#i_12680850 ? should (($x - $*TOLERANCE) =~= $x) ~~ True the same way ($x + $*TOLERANCE) =~= $x does?
Zoffix It's not how it's calculated 14:03
$*TOLERANCE is relative
MasterDuke i know 14:04
Zoffix The question is: (($x - Ī”) =~= $x) ~~ True the same way ($x + Ī”) =~= $x
That is, always use RHS for the item to calculate relative difference off of rather than max(LHS, RHS)
MasterDuke yeah, that's what i intended to ask, but a better wording 14:05
TimToady I don't think a geometric difference has to be arithmetically symmetrical 14:08
MasterDuke i know the serious math around differences and errors and such is more complicated (non-intuitive?) than one might think 14:11
so i don't know whether it's better to be more mathematically rigorous or more DWIM'y 14:13
TimToady so I think calculating a geometric difference and then applying Ā± Ī” to a privileged argument is wrongish 14:14
Zoffix agrees 14:15
TimToady and max is the saner approach, even though it may be surprising to people who expect Ā± Ī” semantics
Zoffix Currently =~= doesn't care which side you put your args on 14:16
TimToady that's why it was written that way
MasterDuke then if i were to write up some docs for =~=, would anybody object if i explicity mentioned that it doesn't do Ā± Ī”?
Zoffix The confusion is due to thinking of it as absolute difference with tolerance set as "percent of" but failing to think about percent of what :)
MasterDuke, sounds like a good idea. 14:17
TimToady it'll be less surprising to people who habitually put the constant on the left of comparisons to catch 5 = $x vs 5 == $x too
MasterDuke: yes, education is probably the best approach here 14:18
MasterDuke sounds good that's what i'll do 14:19
Zoffix It's amazing how much slower JVM is compared to MoarVM. I'm assuming nqp's make m-test/j-test runs the same suite of tests... 14:37
12 wallclock secs for MoarVM / 352 wallclock secs for JVM 14:38
m: say 352/12
camelia rakudo-moar f19241: OUTPUTĀ«29.333333ā¤Ā»
psch well, compiling to moar means compiling to code that feeds essentially a giant switch/case in C 14:39
compiling to jvm means compiling to java classes
that's not to say that there's no way we could get nqp-j faster 14:40
but i don't think we have anyone around that (1) knows enough and (2) cares
with intent of being fair, (2) should probably read "cares and has time" or somesuch vOv 14:41
tadzik the testsuite is a massive amount of small files, which is not something that JVM excels at :) 14:43
(apart from other things)
psch that's another great point, catching up via JIT means having enough runtime to do so
and the jvm is known for slow startup and a great JIT 14:44
tadzik I think niecza used to have an eval server that it used to run the tests, to save on startup time
psch we do have that for rakudo make test
i don't think we use it for nqp make test
tadzik ah
psch it still doesn't redeem r-j, fwiw
but i don't think it's factor 30, more like 10 to 15, at a guess
tadzik does rakudo-j actually still come out ahead in long-running, computationally intensive tasks? 14:45
psch probably not
Zoffix Hm, tags can't be passed via a PR... how do I go about step 6 in github.com/perl6/nqp/blob/master/d..._guide.pod ?
And same for Rakudo too
psch Zoffix: i think nqp is CLA-free, but rakudo wouldn't be 14:46
...or maybe it's the other way around
Zoffix CLA? Contributor License Agreement? What's that about
psch in any case, tagging via PR doesn't work, but if you need it in the next 2-3 hours i can do that for you
Zoffix: basically "i have copyright, but TPF can use it"
Zoffix Is that to get commit bit?
psch yeah
Zoffix Where do I sign? :)
psch it's on perl.org somewhere i think 14:47
blob.perl.org/perlweb/foundation/le...es/cla.pdf
note though, it takes somewhere in the region of 4 months from sending it (from europe...) until it's aknowledge by TPF :)
Zoffix It requires mailing? How 20th century :) 14:48
psch *acknowledged
jnthn Zoffix: I can give you an NQP commit bit right now, if you don't have one?
Zoffix jnthn, sure, that would be great
jnthn Your github id? 14:49
Zoffix jnthn, zoffixznet github.com/zoffixznet/
jnthn ah, I found you :)
done :)
Zoffix Thanks. jnthn++ 14:50
jnthn back later & 14:51
dalek p: fd633b8 | (Zoffix Znet)++ | tools/build/MOAR_REVISION:
Bump MoarVM version for 2016.06 release
15:08
p: 3083e4d | (Zoffix Znet)++ | VERSION:
Bump VERSION to 2016.06
MasterDuke m: my $*TOLERANCE = 0; say 1 =~= 1 15:18
camelia rakudo-moar f19241: OUTPUTĀ«Falseā¤Ā»
MasterDuke TimToady: ^^^^ is expected? currently, setting $*TOLERANCE = 0 means any comparison will fail 15:19
Zoffix 23:29* TimToadydoesn't believe in "zero tolerance" :) 15:20
irclog.perlgeek.de/perl6/2016-06-03#i_12603717
MasterDuke ha 15:21
i'll probably mention that behavior also 15:22
psch i really like that 15:23
Zoffix MasterDuke, BTW, not sure if you spotted that for your docs, but if either arg to =~= is zero, the comparison will be absolute, not relative, and |non-zero-arg| has to be smaller than $*TOLERANCE 15:38
MasterDuke yep, i have some words to that effect 15:39
but i will definitely want people to make sure what i say is correct (both to the code and mathematically) 15:41
dalek p: a334a13 | (Zoffix Znet)++ | docs/release_guide.pod:
Fix incorrect URL
16:05
MasterDuke first stab at documenting =~=, github.com/perl6/doc/pull/604 16:07
Zoffix This sounds wrong. "it calculates the absolute difference between the non-zero side and $*TOLERANCE." Maybe "it checks the absolute difference between the arguments is less than $*TOLERANCE"? 16:11
MasterDuke ahh, that is better 16:30
Zoffix ./perl6-j tools/build/install-core-dist.pl /home/zoffix/CPANPRC/rakudo/install/share/perl6 16:55
===SORRY!===
setcodeobj can only be used with a CodeRef
Any idea what to do?
in block <unit> at tools/build/install-core-dist.pl line 18 16:56
timotimo do we already have debug_name in our jvm port? the error could output the name of the repr and the debug_name of the stable together with that error ...
Zoffix Should I just ignore that for the release? 16:57
timotimo we're not promising jvm support again, so ... dunno :| 16:58
bartolin Zoffix: that's the bug which nine++ and psch++ are hunting for more than two weeks. I'm sure we cannot resolve it now -- so ignoring it is probably the only option 17:00
Zoffix Thanks.
bartolin IIRC rakudo-j did not install on 2015.05 as well 17:01
timotimo oh, that's the one! mastframes and such
bartolin *nods*
Zoffix mst, how do I clone the PR? 17:22
mst Zoffix: help.github.com/articles/checking-...s-locally/ 17:24
Zoffix Well, it's better but less than perfect. The "command line" thing could list git clone github.com/tbrowder/doc.git; git checkout whatever-the-branch-is 17:32
mst++
t/spec/S17-supply/syntax.t is hanging :( 17:34
I guess I can just make a GreaseMonkey script to add what I want.
Zoffix always forgets about that option
mst Zoffix: however, that would be WRONG 17:36
Zoffix: a PR need not be all of the commits in the branch, for example
Zoffix Why not?
New commits would show up in the PR
So regardless if I pull it from a commit or from the breanch, I get the same thing 17:37
s/commit/PR/; s/breanch/branch/;
mst mm 17:40
Zoffix: I'm still confused why you think the more complicated thing would be better than how it currently works 17:42
Zoffix: also, github.com/ingydotnet/git-hub is your friend 17:43
Zoffix I don't keep the repo around. The instructions start off with "git checkout -b tbrowder-perl6-docs master" which is already something I can't run.
heh 17:45
I like GitHub's website. I don't like command line :P
mst but github's website doesn't have a rebase button 17:51
so you're stuck with CLI for most merges anyway
Zoffix I'm having trouble running make stresstest because t/spec/S17-supply/syntax.t keeps freezing 17:56
What do I do in these situations?
4/7 tests fail in t/spec/integration/advent2014-day05.rakudo.moar too :/
mst Zoffix: WD40 17:58
Zoffix heh
timotimo i didn't know wd40 could do anti-freeze 17:59
Zoffix tries to run this on a differnet box 18:00
mst timotimo: it also does anti-cocaine-addicts quite well 18:18
if they won't stop snorting it in the toilets of your bar, you spray all the flat surfaces with WD40 and then throw out anybody who gets a nosebleed 18:19
timotimo o_O
i might be anti-cocaine-addicted 18:20
because i get nosebleeds regularly during some parts of the year
Zoffix So you covert all the surfaces with WD40 and hope the addicts don't own two credit cards? :) 18:23
*cover 18:24
I'm gonna chuck up my failures to issues with the VM, because Perl 5's build was freezing the other day too. 18:32
I removed /syntax.t and now it stuck t/spec/S17-promise/start.t is freezing too. I ran it on my Linode server though and everything is fine.
timotimo oh damn 18:35
again with the "only hangs if run in the test suite"?
Zoffix As compared top what? Just running it on its own?
to* 18:36
timotimo yeah
Zoffix t/spec/S17-promise/start.t still freezes after ok 18 - buf8.new in many start blocks does not explode
Only on the VM. Worked fine on Linode. 18:37
t/spec/integration/advent2014-day05.rakudo.moar fails on both tho
Parse errors: Bad plan. You planned 7 tests but ran 3.
Hm. Type check failed in binding result; expected Any but got Mu (Mu) 18:39
timotimo you have to do some gymnastics to get a Mu by accident 18:41
Zoffix m: gist.github.com/zoffixznet/de7e553...91c0910fb1
camelia rakudo-moar f19241: OUTPUTĀ«Memory allocation failed; could not allocate 4 bytesā¤Ā»
Zoffix :/
timotimo wow, that machine doesn't even have 4 bytes of free space! 18:42
Zoffix m: my $supplier = Supplier.new; my $supply = $supplier.Supply; my @seen; $supply.act: { .say }; await do for 1..5 { start { $supplier.emit($_) } } 18:45
camelia rakudo-moar f19241: OUTPUTĀ«1ā¤2ā¤3ā¤4ā¤5ā¤Type check failed in binding result; expected Any but got Mu (Mu)ā¤ in block <unit> at <tmp> line 1ā¤ā¤Ā»
Zoffix m: my $supplier = Supplier.new; my $supply = $supplier.Supply; my @seen; $supply.act: { .say }; await (1..5).map: { start { $supplier.emit($_) } }
camelia rakudo-moar f19241: OUTPUTĀ«1ā¤2ā¤3ā¤4ā¤5ā¤Type check failed in binding result; expected Any but got Mu (Mu)ā¤ in block <unit> at <tmp> line 1ā¤ā¤Ā»
Zoffix m: my $supplier = Supplier.new; my $supply = $supplier.Supply; my @seen; $supply.act: { .say }; (1..5).map: { start { $supplier.emit($_) } }; sleep 2 18:46
camelia rakudo-moar f19241: OUTPUTĀ«1ā¤2ā¤3ā¤5ā¤4ā¤Ā»
Zoffix bisect: my $supplier = Supplier.new; my $supply = $supplier.Supply; my @seen; $supply.act: { .say }; await (1..5).map: { start { $supplier.emit($_) } } 18:48
bisectable Zoffix: (2016-06-17) github.com/rakudo/rakudo/commit/627dcf4
Zoffix I love that bot
timotimo o_O 18:53
good catch
Zoffix m: await start { Mu }; 18:54
camelia rakudo-moar f19241: OUTPUTĀ«Type check failed in binding result; expected Any but got Mu (Mu)ā¤ in block <unit> at <tmp> line 1ā¤ā¤Ā»
timotimo twitter.com/randal_olson/status/74...5497123840
we probably should allow Mu to be returned from a start block and into await 18:55
Zoffix m: my $x = start { Mu }; sleep 1; say $x.result 18:57
camelia rakudo-moar f19241: OUTPUTĀ«Type check failed in binding result; expected Any but got Mu (Mu)ā¤ in block <unit> at <tmp> line 1ā¤ā¤Ā»
Zoffix m: my $x = start { Mu }; sleep 1; say $x.status 18:58
camelia rakudo-moar f19241: OUTPUTĀ«Brokenā¤Ā»
Zoffix Any idea how to fix this? This is --ll-exception: gist.github.com/zoffixznet/7a43207...fe61d3e541 19:02
timotimo it's showing where the exception gets thrown from when you access the result, doesn't it? 19:03
not where exactly the exception was generated
Zoffix I guess. It's showing .result and then some sort of NQPHLL stuff 19:05
timotimo yeah, the "unhandled exception" stuff 19:06
MasterDuke timotimo: huh, any way to get a better core dump? 19:07
timotimo oh, you're not in #perl6?
MasterDuke not right now
timotimo well, i'm not 100% sure how core dumps are supposed to work; i thought having the core dump would make it unnecessary to have the binaries and libraries on your computer
perhaps i can get the exact code and data you have on your machine and try to reproduce the segfault, maybe without valgrind 19:08
Zoffix m: class Foo { method bar (\result) { say result} }; Foo.new.bar: Mu 19:09
camelia rakudo-moar f19241: OUTPUTĀ«Type check failed in binding result; expected Any but got Mu (Mu)ā¤ in method bar at <tmp> line 1ā¤ in block <unit> at <tmp> line 1ā¤ā¤Ā»
timotimo yeah, something isn't accepting Mu even though it might be interesting to accept it 19:10
Zoffix Likely Vow.keep 19:11
Zoffix tries a build
MasterDuke new error, 'Internal error: invalid thread ID 77939872 in GC work pass' 19:14
another new one, 'Internal error: zeroed target thread ID in work pass' 19:15
timotimo right, that's what made me think memory corruption
MasterDuke moarvm, nqp, rakudo, doc, Pod::To::HTML, and uri are up to date 19:16
the only difference is my modification to htmlify.p6
gist.github.com/MasterDuke17/d06f0...426ef33d52 19:17
Zoffix What does this mean? $!promise!Promise::keep(result) 19:31
When $!promise is a Promise object
Like what is it calling. Because my interpretation leads me to an infinite loop :/ 19:32
Oh, I was looking at the public keep... neverm,ind 19:33
(rebooting my VM fixed the spectest hanging issues BTW) 19:50
And I have the fix for the Mu. Just running the spectest now
timotimo weird. 19:52
Zoffix never mind... it's freezing again ~šŸ˜æ~ this is annoying 20:01
timotimo yes, very
we've been known to fudge flappy or hangy tests in the past for releases
Zoffix I don't think it's the tests' problem, since they do work on another box 20:17
(and as I've mentioned, my last attempt to build Perl 5 froze too) 20:18
PR to fix the spectest failure: github.com/rakudo/rakudo/pull/792 20:28
the Mu stuff
Or should I just make that part of the Release PR? 20:47
Zoffix will
MasterDuke does anybody have an opinion on RT #128406? should a Scalar's .perl look like its value's .perl? 21:29
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=128406
timotimo ugh, RT and its "hide quoted text" feature 22:00
well, first of all i'd expect $x = scalar-make to assign the contents of the scalar that was made into the scalar for $x; for the other thing you'd have to bind 22:02
also, methods called on a scalar will decont and resolve on the contents
if you'd get the .perl of the scalar + its value every time you .perl on something that's in a scalar, you'll have A Bad Timeā„¢ in my opinion 22:04
Zoffix I made release tarball for rakudo and unpacked it elsewhere. Is it normal to see those few missing tests in make stresstest for that tarball? gist.github.com/zoffixznet/5636e56...be3ed0da84 22:25
timotimo did you make manifest? 22:26
Zoffix no idea. I'm just following the instructions on github.com/rakudo/rakudo/blob/nom/..._guide.pod 22:27
(#14)
timotimo huh, was make manifest removed or something? 22:29
Zoffix ĀÆ\_(惄)_/ĀÆ
timotimo or maybe that's only in the star release process and i'm confusing the two
Zoffix I'm done with making release files. I need someone to upload them to rakudo.org: temp.perl6.party/2016.06-release/ 23:01
And this is the PR for Rakudo. Someone needs to create the tag after merging: github.com/rakudo/rakudo/pull/793 23:02
Hm. Apparently this commit is causing installation failure on Arch Linux (see #perl6 convo): github.com/rakudo/rakudo/commit/c7...9acc1caf55 23:18
Error: dpaste.de/sg5x 23:21
shirt 23:26
ABORT! ABORT! :)
*shit
I can replicate the issue with make DESTDIR="/tmp/tmp.RgEF7fzXbT/perl" install
timotimo has no clue about DESTDIR 23:28
Zoffix This is the error I got gist.github.com/zoffixznet/f814e15...7d96cafb3e 23:29
timotimo does that file exist btw? 23:30
Zoffix Yeah. This is what's inside of it: temp.perl6.party/precomp-bug-file 23:32
.ask nine would you have any idea how to fix this issue? It happens when DESTDIR is specified for make install and it's blocking the release: irclog.perlgeek.de/perl6-dev/2016-0...i_12690874 23:33
yoleaux2 Zoffix: I'll pass your message to nine.
timotimo it doesn't look b0rked at least
Zoffix Since (I'm guessing) this would affect anyone trying to make a package + other users. I say we delay the release until whenever the issue can be fixed. 23:36
Way over my head to even try to fix it, unfortunately :(
MasterDuke unrelated to the immediately above, but interesting behavior. i added a .perl method to Scalar.pm and that causes a spectest run (no multiple jobs) to chew up >6.5gb ram by the time it hits t/spec/S02-types/WHICH.t 23:38
the method just called self.perl. which, on the plus side, gave a possibly more useful result than before 23:41
also unrelated (i think), but with a completely unmodified but up to date moar, nqp, and rakudo, i'm consistently getting failures and coredumps/segfaults when running t/spec/S17-lowlevel/lock.t 23:45
Zoffix It's just floppy with my current runs. 23:49
(has been for ages) 23:50
MasterDuke huh, don't remember this many problems with it before, but i may just have gotten lucky then 23:52