travis-ci Rakudo build passed. Zoffix Znet 'Merge pull request #904 from tbrowder/new-test 02:30
travis-ci.org/rakudo/rakudo/builds/167705475 github.com/rakudo/rakudo/compare/8...c0750171cd
p3rln00b Internet dead at home for some reason :( not a good release day start :( 06:39
yoleaux2 14 Oct 2016 21:53Z <jnthn> p3rln00b: I'd guess so, but do a spectest to be sure
Zoffix \o/ 06:44
Though, I can always tether my lappy to my phone if I had to.
dalek kudo/nom: 2c681c5 | (Zoffix Znet)++ | docs/ChangeLog:
Log all changes to date

Documents commits: 6283124 bfe6219 e5df7a7 5a79e22 8df0965 bf7945e 7f16cbb b08ef96 8268ffb		 07:11
[Tux] This is Rakudo version 2016.09-199-g41c0750 built on MoarVM version 2016.09-47-g736364c 07:37
csv-ip5xs 3.125
test 15.766
test-t 6.888
csv-parser 17.313
dalek kudo/nom: 873e60f | (Zoffix Znet)++ | src/core/Mu.pm:
Remove unused Mu.dispatch:<.^> method

The code is not hit during stresstests. Per discussion[^1] and confirmation[^2], this code is no longer used and can be removed. Stresstest passes.
  [1] github.com/perl6/doc/issues/970#is...-253824298
  [2] irclog.perlgeek.de/perl6-dev/2016-...i_13405760		 07:40
ast: 53bdf26 | usev6++ | S (3 files):
Fudge tests for JVM; use ticket number
 07:44
Zoffix psch, you around? So the closure nqp failures are due to an old bug, but what about the last two failures? Can they be ignored for the release? gist.github.com/zoffixznet/448d79d...c0eb803e83 07:48
travis-ci Rakudo build errored. Zoffix Znet 'Log all changes to date 07:55
travis-ci.org/rakudo/rakudo/builds/167837220 github.com/rakudo/rakudo/compare/4...681c55520d
bartolin committable6: 2016.09,HEAD say (my int $ = 2**32) * (my int $ = 2**63) 07:56
committable6 bartolin, ¦«2016.09»: 0␤¦«HEAD»: This type cannot unbox to a native integer: P6opaque, Failure␤ in block <unit> at /tmp/5gdU3BwADu line 1␤ «exit code = 1»
Zoffix I guess I have my answer. The test was addded just 2 days ago: github.com/perl6/nqp/commit/682f82...ae07044f59 07:57
psch yeah, pmurias is pretty awesome about nqp tests
anyway, the failure is about autoboxing, and is probably something we should look into
might relate to natives on jvm i think
Zoffix should look into... you mean before the release? 07:58
psch no, the bug is an old one, we just didn't test it before
i'm not sure in how far it actually does impact rakudo either 07:59
Zoffix bartolin, oh, I was meant to fix that.
I thought I did
AlexDaniel when?
bartolin r: my int $iL = 2**62; say $iL * $iL 08:00
camelia rakudo-moar 873e60: OUTPUT«This type cannot unbox to a native integer: P6opaque, Failure␤ in block <unit> at <tmp> line 1␤␤»
..rakudo-jvm 2a1605: OUTPUT«0␤»
AlexDaniel m: say (my int $ = 2**32) * (my int $ = 2**63)
camelia rakudo-moar 873e60: OUTPUT«This type cannot unbox to a native integer: P6opaque, Failure␤ in block <unit> at <tmp> line 1␤␤»
Zoffix When what? I meant I said I'll fix it and I forgot :)
AlexDaniel ah ok :) Just wanted to note that whateverables are currently behind HEAD for one or two commits 08:01
bartolin I'm somewhat confused. that test failed with 'Numeric overflow' on rakudo-j a few days ago 08:02
dalek p: 298e228 | (Zoffix Znet)++ | t/qast/01-qast.t:
Temporarily comment out tests failing on JVM

The tests were added in the past few days, but the issues existed on JVM for a while[^1][^2]. Comment the tests out for the release, to avoid any confusion downstream, when someone notices "new" failures.
This commit will be reverted after the release.
  [1] irclog.perlgeek.de/perl6-dev/2016-...i_13401309
  [2] irclog.perlgeek.de/perl6-dev/2016-...i_13407254		 08:03
bartolin and now it dies with the above error. but with --optimize=1 it returns 21267647932558653966460912964485513216 (no numeric overflow anymore)
Zoffix bartolin, it's meant to return 0. It was made to return a Failure recently, but later it was discussed that natives should not return Failures and returning 0 is perfectly fine. Whatever tests expect a Failure were added as part of coverage work and I'll revert them shortly. The optimize stuff is likely due to dispatch bug with nativevs 08:05
yoleaux2 08:04Z <japhb> Zoffix: Thanks!
Zoffix (there's a ticket for it) 08:06
bartolin Zoffix: Ahh, I see. Must have missed that discussion. Thanks! 08:07
the ticket is RT #129813, probably 08:09
Zoffix Aforementioned discussion: irclog.perlgeek.de/perl6-dev/2016-...i_13372432 08:12
Well, it starts a few lines above that; at irclog.perlgeek.de/perl6-dev/2016-...i_13372307
bartolin Zoffix++ 08:13
Zoffix .tell p3rln00b revert github.com/perl6/nqp/commit/298e2281ec after the release 08:15
yoleaux2 Zoffix: I'll pass your message to p3rln00b.
psch huh 08:24
the last failures in qast.t are actually automatic *un*boxing
...i suppose i shoulda seen that, cause it says so in the test results 08:25
i don't think i understand the test 08:26
dalek kudo/nom: 8ad885f | (Zoffix Znet)++ | / (2 files):
Remove overflow check on native infix:<*> and infix:<**>

To preserve 1-type-of-return and inlining, we do not[^1] do overflow checks on native subs.
  [1] irclog.perlgeek.de/perl6-dev/2016-...i_13372307		 08:31
ast: c8fc433 | (Zoffix Znet)++ | S32-num/int.t:
Remove tests that expect overflow checks from native subs

The tests were added recently, as part of coverage work and they test behaviour that is unwanted and has been removed[^1] from rakudo.
  [1] github.com/rakudo/rakudo/commit/8ad885f0ab		 08:32
psch pff, silly jvm/jdb, can't even reenter nqp code... 09:13
"SIGSEGV (0xb) at pc=0x0000000000000001" 09:14
travis-ci Rakudo build passed. Zoffix Znet 'Remove overflow check on native infix:<*> and infix:<**> 09:17
travis-ci.org/rakudo/rakudo/builds/167844903 github.com/rakudo/rakudo/compare/8...d885f0ab8b
psch okay, so apparently nqp-j feels like having an intBoxType doesn't necessarily mean that a variable that gets assigned an int needs to be boxed into the given intBoxType 09:27
it's perfectly okay with using BOOTInt 09:28
Zoffix :( t/04-nativecall/16-rt125408.t keeps failing when I'm running a release test on my VM :/ 09:40
And unless it's a flapper, the issue is due to updated nqp/moarvm 09:49
Zoffix tries building HEAD of each
Ah. It'd help if I updated my test repos :} 10:13
There's no way for me to lose the ability to delete perl6/nqp repo without losing my org admin status, is there? 10:26
I'm paranoid about deleting perl6/nqp instead of zoffixznet/nqp during pre-release tests :|
nine Inline-Perl5 (redesign_v6_inline *)> perl6 -e 'Distribution::Path.new($*CWD, :file("META.info".IO))' 10:27
No such method 'IO' for invocant of type '<anon|118534656>'
This could be a rakudo regression ^^^ 10:28
Zoffix m: class {}.IO
camelia rakudo-moar 8ad885: OUTPUT«No such method 'IO' for invocant of type '<anon|63061472>'␤ in block <unit> at <tmp> line 1␤␤»
Zoffix star: class {}.IO
camelia star-m 2016.04: OUTPUT«Method 'IO' not found for invocant of class '<anon|57619280>'␤ in block <unit> at <tmp> line 1␤␤»
Zoffix s: Distribution::Path, 'new', \($*CWD, :file("META.info".IO)) 10:29
SourceBaby Zoffix, Sauce is at github.com/rakudo/rakudo/blob/8ad8...on.pm#L122
nine m: Distribution::Path, 'new', \($*CWD, :file("META.info".IO))
camelia rakudo-moar 8ad885: OUTPUT«WARNINGS for <tmp>:␤Useless use of constant string "new" in sink context (lines 1, 1)␤»
Zoffix Wasn't there a change from a role to a class? 10:30
nine m: Distribution::Path.new($*CWD, :file("META.info".IO))
camelia rakudo-moar 8ad885: OUTPUT«No meta file located at /home/camelia/META.info␤ in block <unit> at <tmp> line 1␤␤»
Zoffix 'cause there's a weird quirk that a role is Cool and Cool has .IO
m: role {}.IO
camelia rakudo-moar 8ad885: OUTPUT«No such method 'IO' for invocant of type '<anon|48705520>'␤ in block <unit> at <tmp> line 1␤␤»
Zoffix Oh dafuq
m: role {}.new.IO
camelia rakudo-moar 8ad885: OUTPUT«No such method 'IO' for invocant of type '<anon|47906832>'␤ in block <unit> at <tmp> line 1␤␤»
Zoffix m: say role {} ~~ Cool
camelia rakudo-moar 8ad885: OUTPUT«True␤»
Zoffix is uber confused now 10:31
m: Cool.IO
camelia ( no output )
nine I got the error with "This is Rakudo version 2016.09-116-g2a2f26c" on my laptop. Upgrading rakudo right now. 10:32
Oh. It's actually fixed in current nom :) 10:35
So there was a regression but also a fix :)
Sorry for the noise 10:36
lizmat Zoffix: still time to get in a JVM fix ? 10:39
see last mail of bartolin 10:40
j: class { has int $!n = 0; method x ($!n) {} }.new.x: 42
camelia rakudo-jvm 2a1605: OUTPUT«org.perl6.nqp.sixmodel.reprs.P6OpaqueBaseInstance$BadReferenceRuntimeException: Cannot access a native attribute as a reference attribute␤ in method x at <tmp> line 1␤ in block <unit> at <tmp> line 1␤␤»
Zoffix lizmat, if someone knows how to fix it, sure. I'm still waiting for MoarVM release 10:43
lizmat well, it's a bandaid fix really, to make sure List.tail works on JVM again
dalek kudo/nom: 666128f | lizmat++ | src/core/Rakudo/Internals.pm:
Make List.tail work on JVM for now

We cannot presently bind native attributes in a signature yet.		 10:47
stmuk hmmm wondering whether to delay Rakudo * until FreeBSD/OpenBSD & Linux (HLE CPUs) works? 11:04
timotimo stmuk: any chance a bios update could potentially fix the problem on all those machines?
stmuk well maybe microcode update could fix Linux 11:05
timotimo allegedly not 11:07
but a friend told me a bios update would turn the feature off during boot
stmuk I don't think HLE is the root cause since I've seen the bug (or similar) on all BSD systems with old processors 11:08
eg. qemu virtual CPU & FreeBSD
timotimo does the documentation say unlocking a mutex that's not locked at that moment is illegal?
stmuk on what platform? 11:10
bbl 11:12
timotimo i guess i'll have a quick look if libuv gives us the ability to try to lock something only if it isn't currently locked, without blockin 11:18
then we can just do that immediately before unlocking the mutex and we won't end up unlocking an unlocked mutex 11:19
how's that sound?s
nine racy?
timotimo yeah, there's uv_mutex_trylock
it'd be racy if we looked if the lock is unlocked and then lock it 11:20
because between finding out it isn't locked and unlocking it, some other thread may have locked it
nine But if we check if it's locked and we find it to be locked, so we think it's good and just before we unlock it, someone else beats us there? 11:22
timotimo wrong. if it's locked, we know we're owning the lock
of course it'd be better if we could figure out why we end up with an unlocked mutex that we're trying to unlock again in the first place 11:23
nine Then it's fine :)
That's the real question, yes
timotimo even though stmuk has been complaining about this for a long time, and some other users have recently started hitting this bug, nobody wanted to do anything about it yet 11:24
actually ... i think i'll even guard this shitty hack with an environment variable 11:27
timotimo suddenly learns about secure_getenv 11:28
hm, seems like you can compile libuv with debugging and get it to error when you do a destroy, a lock, or an unlock where you're not supposed to 11:30
so maybe we can debug this on a non-b0rked linux system that way?
... how do we actually build libuv at all? 11:31
ugh, i'm having a really hard time finding the ticket for this 11:43
stmuk: what's the RT again?
nine m: role Foo {}; my $bar = 1; $bar does Foo unless $bar.does(Foo); 11:47
camelia rakudo-moar 666128: OUTPUT«WARNINGS for <tmp>:␤Useless use of $bar in sink context (line 1)␤»
nine Ha! a new useless useless warning ^^^!
TimToady: ^^^
At least Perl 6 makes it easier to edit a postfix unless into an unless statement :) 11:49
AlexDaniel what does it mean? ｢$bar does Foo｣
nine mixes the role into the object 11:50
AlexDaniel m: role Foo {}; my $bar = 1; $bar does Foo unless $bar.does(Foo); say $bar.WHAT
camelia rakudo-moar 666128: OUTPUT«WARNINGS for <tmp>:␤Useless use of $bar in sink context (line 1)␤(Int+{Foo})␤»
AlexDaniel indeed
timotimo pff. on linux, libuv already sets the mutex type to ERRORCHECK, which means a re-unlock is already supposed to cause an abort() immediately 11:52
(the abort is added by libuv)
lizmat jnthn_: is there a compelling reason why Str.match returns a List instead of a Seq ? 11:54
(when returning more than one Match) 11:55
bartolin_ timotimo: it's issue 410 for MoarVM, isn't it?
timotimo ah
that's why i couldn't find it on rt
stmuk: can you try out a patch for me on the systems that explode? 11:59
because i just pushed a branch to moarvm that makes extra double sure that that unlock can't happen if the lock before that didn't happen 12:02
stmuk timotimo: sure! 12:03
timotimo:f2369? 12:05
timotimo 9b12a49
stmuk ah I see the branch 12:08
timotimo: YES! it fixes panda install on FreeBSD 11 12:29
timotimo o_O
okay, could you perhaps put a hardware watchpoint on the variable that has_user_threads reads?
because if this fixed it, that value seems to change during the body of the multi_cache_add function 12:30
well, at least i don't see a reason why this shouldn't be on master 12:32
stmuk timotimo: I can do this later but I was going out shortly
timotimo OK
i'm glad this fixed it
i hope this is the same problem linux with broken HLE has? 12:33
stmuk the stacktraces looked v similar
timotimo as long as multi_cache_add was on the stack trace, it'll potentially be the right thing 12:34
stmuk timotimo: OK I can do further testing today early Euroish evening time
timotimo thing is, it shouldn't be possible for this to fix anything
oh
yeah, it is possible i guess
if you make enough new threads that the thread id wraps
stmuk bbfn 12:35
timotimo does zef or panda create about 2**32 or 2**64 threads to install stuff? 12:36
lizmat timotimo: pretty sure it doesn' 12:38
t
timotimo yeah, i'm pretty sure, too 12:39
it'd probably take a couple of days to create that many threads
lizmat afk& 13:09
timotimo m: Thread.new for ^(2**32) 13:16
camelia rakudo-moar 666128: OUTPUT«Required named parameter 'code' not passed␤ in block <unit> at <tmp> line 1␤␤»
timotimo m: Thread.new(:code({ sleep 10 })) for ^(2**32)
camelia rakudo-moar 666128: OUTPUT«Memory allocation failed; could not allocate 131072 bytes␤»
timotimo that was fast
yeah, that kind of code gets you OOM-killed rather quickly :) 13:17
dalek ast: a08298d | (Harrison Chienjo)++ | S29-os/system.t:
Tests for Proc.command and Proc.signal (#169)

  * Add test for Proc.command.
  * Fix missing last parameter.
  * Add test for proc.command returned by shell().
  * Add .signal test for Proc.
  * Use correct name.
  * Fix wrong name in test description.
58047e6 | moritz++ | S09-typed-arrays/native-decl.t: Very basic my str @ tests		 15:26
TimToady nine: thanks, put it into my uu file :) 16:19
Zoffix Release! Release! Release! Release! 16:51
Zoffix is impatient :D
mst bloody canadians 16:54
moritz so, who does the release?
Zoffix NeuralAnomaly does.
But we're all waiting for jnthn++ to cut MoarVM release :) 16:55
mst WE DEMAND MOAR 17:11
Zoffix: NeuralAnomaly is yet another of your botswarm?
lucasb_ is waiting too :)
Zoffix mst, yup
geekosaur zoffix is a bit botty >.> 17:12
moritz taking over the world with IRC and release bots. I, for one, welcome our now electronic overlords! 17:14
Zoffix \o/
nine Seems like we really need a MoarVM release bot ;) 17:15
ast: c8889fc | moritz++ | S03-operators/autoincrement.t:
Test pre- and postfix autoincrement on Num
 17:37
Zoffix moritz, I guess I should've mentioned that coverage report is a bit outdated :} 17:38
Not that I mind extra tests.
moritz arglbargl
Zoffix :} 17:39
The other one are in github.com/perl6/roast/commit/2a3c...21f87da80f
moritz and this being roast, there are least three sensible places where such tests should go 17:40
Zoffix nods
dalek ast: c64cd86 | moritz++ | S03-operators/autoincrement.t:
Revert "Test pre- and postfix autoincrement on Num"

This reverts commit c8889fc78a3b46a4721406b7d787fe1ccf8c1df1.
Turns out those ops were already covered in commit 2a3cdb2e257e97d8c6dafefecc8f6221f87da80f / file S02-types/num.t		 17:41
kudo/nom: 1acf5bf | TimToady++ | src/Perl6/Actions.nqp:
does is a mutator, so should want its left arg
 17:57
TimToady nine: you can go ahead and flip your 'unless' back if you like, though seems to me 'does' should be smart enough not to reapply a role, which oughta be safe since roles are immutable 17:58
and reapplying a role ought to be idempotent 18:00
nine TimToady: thanks! That means, I'm now gonna have to find out why exactly I need that unless. I'm sure I've tried it without at first. 18:06
Zoffix m: role Foo {}; my $x = 42; quietly $x does Foo for ^10; dd $x 18:08
camelia rakudo-moar 666128: OUTPUT«Int+{Foo}+{Foo}+{Foo}+{Foo}+{Foo}+{Foo}+{Foo}+{Foo}+{Foo}+{Foo} $x = 42␤»
Zoffix s: &infix:<does> 18:09
SourceBaby Zoffix, Sauce is at github.com/rakudo/rakudo/blob/6661...ors.pm#L15
timotimo .comb(0) is apparently the same as .comb(1) 18:48
do we want that?
Zoffix m: 'foo'.comb(-1000000).say 18:49
camelia rakudo-moar 1acf5b: OUTPUT«(f o o)␤»
Zoffix IMO throwing would be good.
timotimo m: "hello".comb(NaN) 18:57
camelia rakudo-moar 1acf5b: OUTPUT«Cannot resolve caller comb(Str: Num); none of these signatures match:␤ (Cool $: *%_)␤ (Cool $: Regex $matcher, $limit = Inf, *%_)␤ (Cool $: Str $matcher, $limit = Inf, *%_)␤ (Str:D $: *%_)␤ (Str:D $: Int:D $size, $limit = *, *%_)…»
Zoffix Well, with it being 9PM in Prague, I don't think there'll be a release today.... So I'm free to go out, get booze, and get drunk :P 19:00
mst oh, good, you're back in the fold again
I was worried there for a minute
timotimo that's okay
Zoffix lol
mst, I didn't drink since last Friday. 19:01
It's very un-Zoffix-like
lucasb_ stay healthy Zoffix++
mst Zoffix: I'm so sorry
Zoffix lol
mst ugh. at some point I should try and write an irssi filter that strips mangled ++s like that 19:02
lucasb_ .comb returns nonsense values when you pass non-positive and a limit 19:03
m: say 'abcdef'.comb(0, 2).perl
camelia rakudo-moar 1acf5b: OUTPUT«("b", "c").Seq␤»
lucasb_ m: say 'abcdef'.comb(-1, 2).perl
camelia rakudo-moar 1acf5b: OUTPUT«("c", "d").Seq␤»
timotimo but is that really nonsense?
m: say 'abcdef'.comb(-2, 2)'perl
camelia rakudo-moar 1acf5b: OUTPUT«===SORRY!=== Error while compiling <tmp>␤Two terms in a row␤at <tmp>:1␤------> say 'abcdef'.comb(-2, 2)⏏'perl␤ expecting any of:␤ infix␤ infix stopper␤ postfix␤ statement end␤ statement…»
timotimo m: say 'abcdef'.comb(-2, 2).perl
camelia rakudo-moar 1acf5b: OUTPUT«("d", "e").Seq␤»
timotimo m: say 'abcdef'.comb(-3, 2).perl
camelia rakudo-moar 1acf5b: OUTPUT«("e", "f").Seq␤»
timotimo that's so cool
not sensible to keep, though 19:04
timotimo AFK
nine m: role Foo { has @.attrs }; my $i = 1; $i does Foo; $i.attrs.push: 1; $i does Foo; $i.attrs.push: 2; say $i.attrs 19:13
camelia rakudo-moar 1acf5b: OUTPUT«[2]␤»
nine TimToady: ^^^ not as idempotent as it ought to be
Zoffix changed mind 19:21
Don't wanna feel like crap tomorrow :} 19:22
nine Zoffix: that's why I rarely drink these days. Too much productive time lost. And too many awesome things to try :) 19:26
Zoffix :) 19:27
"No appropriate parametric role variant available for 'Inline::Perl5::Perl5Attributes'Compilation failed in require at (eval 1) line 122." 22:00
nine, you around? :)
Full output. That's while trying to install Inline::Perl5 with bleed rakudo: gist.github.com/zoffixznet/578a830...bde0bad386 22:01
lizmat Zoffix: perhaps this is related to TimToady's last commit ? 22:03
aka 1acf5bf88d8aea231509 ? 22:04
Zoffix m: role Foo {}; my $bar = 1; $bar does Foo unless $bar.does(Foo); 22:06
camelia ( no output )
Zoffix m: role Foo {}; my $bar = 1; $bar does Foo unless $bar.does(Foo); dd $bar
camelia rakudo-moar 1acf5b: OUTPUT«Int+{Foo} $bar = 1␤»
Zoffix gonna try to build weithout it 22:08
Hmm... "No need for Perl5Attributes to be parametric": github.com/niner/Inline-Perl5/comm...4002eb36ae 22:10
lizmat is tired and goes to bed 22:15
Zoffix Still fails with TT's change, so I'm betting my money on the above commit 22:17
I mean without TT's commit :) 22:18
lizmat ok, well, it was related to roles
sleep& 22:19
Zoffix night
Well, if I --notest install it, the stresstest seems to pass, so no rush on fixing it :) 22:37
timotimo all those bots run on hack, then? 22:38
Zoffix Just the above two 22:39
timotimo ok 22:40
but you create the data they use on a beefier bot?
obx*
box*
Zoffix The coverage stuff I run on my home box. One of the bots does build each rakudo commit though
timotimo cool 22:41
did you ever have a look at collect.p6c.org?
Zoffix Never heard of it
timotimo it's a monitoring thing 22:42
Zoffix NeuralAnomaly, status 22:48
NeuralAnomaly Zoffix, [✘] Next release is today. Since last release, there are 47 new still-open tickets (1 unreviewed and 0 blockers) and 2 unreviewed commits. See perl6.fail/release/stats for details
Zoffix NeuralAnomaly, status
NeuralAnomaly Zoffix, [✔] Next release is today. Since last release, there are 47 new still-open tickets (0 unreviewed and 0 blockers) and 0 unreviewed commits. See perl6.fail/release/stats for details
timotimo cool :) 22:49
Zoffix NeuralAnomaly, it's time
NeuralAnomaly Zoffix, Oh boy! Really?! We're doing a realease‽‽ YEY!
Zoffix NeuralAnomaly, cut the release
NeuralAnomaly Zoffix, Will do! If you're feeling particularly naughty, you can watch me at perl6.fail/release/progress or go look at some cats icanhas.cheezburger.com/lolcats
Zoffix, ♥♥♥♥♥♥ Prep done
AlexDaniel by the way, what's up with smoke.perl6.org/report ?
dalek p: 7914a19 | (Zoffix Znet)++ | tools/build/MOAR_REVISION:
bump MoarVM version to 2016.10
p: 223373d | (Zoffix Znet)++ | VERSION:
bump VERSION to 2016.10
timotimo oh, the release comes with a java thing now? 22:52
Zoffix What java thing? 22:53
timotimo it's building rakudo-j right now
no, nqp-j
Zoffix No, it's building nqp-j
It does build and test nqp-j, but not rakudo-j
timotimo OK! 22:54
NeuralAnomaly Zoffix, ♥♥♥♥♥♥ nqp tests OK 22:58
timotimo it's building nqp-j again? 23:01
Zoffix Yes. It made the tarball and it's now testing it. 23:02
mst you killed dalek 23:05
* Zoffix is now known as ZoffixWho
Zoffix :D 23:06
I don't think it was me
It was AlexDaniel
AlexDaniel yeah…
NeuralAnomaly Zoffix, ♥♥♥♥♥♥ nqp release tarball tests OK 23:07
Zoffix, ♥♥♥♥♥♥ nqp release DONE 23:08
dalek kudo/nom: 090c392 | (Zoffix Znet)++ | docs/announce/2016.10.md:
Generate release announcement for 2016.10
kudo/nom: 7c62a41 | (Zoffix Znet)++ | tools/build/NQP_REVISION:
[release] bump NQP revision
kudo/nom: eb3123e | (Zoffix Znet)++ | VERSION:
[release] bump VERSION to 2016.10
NeuralAnomaly Zoffix, ♥♥♥♥♥♥ Rakudo stresstest (master) OK 23:15
Zoffix, ♥♥♥♥♥♥ Rakudo stresstest (6.c-errata) OK 23:17
Zoffix, ♥♥♥♥♥♥ Rakudo release DONE 23:25
Zoffix, ♥♥♥♥♥♥ Post: upload tarballs to rakudo.org
Zoffix, 🎺🎺🎺📯📯📯📯📯📯🌈🌈🌈📦📦📦
Zoffix, The release of **Rakudo #104 2016.10** has now been completed
Zoffix, 🎺🎺🎺📯📯📯📯📯📯🌈🌈🌈📦📦📦
NeuralAnomaly celebrates with an appropriate amount of fun
Zoffix NeuralAnomaly, thanks
NeuralAnomaly Zoffix, any time, buddy!
p3rln00b 23:26
yoleaux2 08:15Z <Zoffix> p3rln00b: revert github.com/perl6/nqp/commit/298e2281ec after the release
dalek p: 3e14289 | (Zoffix Znet)++ | t/qast/01-qast.t:
Revert "Temporarily comment out tests failing on JVM"

This reverts commit 298e2281ec01c7c61e446024ca59078e3a3748bb.
Unfudges failing JVM tests		 23:28
Zoffix And now I can retreat to play all three parts of Star Craft II that should finish downloading in 10-15 minutes \o/
dalek kudo/nom: 1942243 | (Zoffix Znet)++ | docs/release_guide.pod:
2016.10 is now in the past
 23:30
kudo/nom: b744de3 | (Zoffix Znet)++ | docs/ChangeLog:
Prep 2016.11 section
 23:35
timotimo only played the first two parts of that 23:37
Zoffix I played them a few times in the past, but never the last one 23:40
timotimo to bed 23:41

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!