Geth rakudo: W4anD0eR96++ created pull request #1734:
Improve Range.minmax on excluded Ranges
05:30
lizmat Files=1239, Tests=76304, 320 wallclock secs (16.00 usr 5.59 sys + 2203.60 cusr 219.13 csys = 2444.32 CPU) 10:16
AlexDaniel releasable6: status 10:38
releasable6 AlexDaniel, Next release in ≈7 days and ≈8 hours. 7 blockers. 224 out of 233 commits logged
AlexDaniel, Details: gist.github.com/fe8e3cb606171477b8...ab64bcfcce
[Tux] Rakudo version 2018.03-233-g430266629 - MoarVM version 2018.03-108-g4034d9def
csv-ip5xs0.914 - 0.958
csv-ip5xs-208.882 - 9.468
csv-parser36.314 - 36.880
csv-test-xs-200.444 - 0.472
test8.669 - 10.252
test-t2.464 - 2.472
test-t --race1.030 - 1.055
test-t-2044.196 - 44.259
test-t-20 --race15.117 - 15.357
12:31
Na reboot: test-t 2.445 - 2.468 14:51
lizmat m: my @a; @a[*-1] = 42; dd @a # smells fishy 20:40
camelia Array @a = []
lizmat m: my @a; @a.ASSIGN-POS(-1,42); dd @a 20:41
camelia Index out of range. Is: -1, should be in 0..^Inf
in block <unit> at <tmp> line 1
lizmat m: my @a; @a.AT-POS(-1) = 42; dd @a
camelia Index out of range. Is: -1, should be in 0..^Inf
in block <unit> at <tmp> line 1
lizmat apparently it's the postcircumfix candidate doing something weird 20:42
Geth ¦ rakudo: zoffixznet self-assigned No such method 'assuming' for invocant of type 'WhateverCode' github.com/rakudo/rakudo/issues/1735
nqp: 22b4b69f6c | (Zoffix Znet)++ | tools/build/MOAR_REVISION
[MoarVM Bump] Brings 4 commits

MoarVM bump brought: github.com/MoarVM/MoarVM/compare/2...2-gfa0fc18 fa0fc18 Merge branch 'lazier_inline_fixups' 9655e15 we can re-use these spesh slots. 8a5615e get rid of spesh retry mechanism 587e08d Fix fixing of wvals during inline
20:45
¦ nqp: version bump brought these changes: github.com/MoarVM/MoarVM/compare/2...2-gfa0fc18 20:46
rakudo: 72b54ddd6f | (Zoffix Znet)++ | tools/build/NQP_REVISION
[NQP Bump] 22b4b69 [MoarVM Bump] Brings 4 commits

NQP bump brought: github.com/perl6/nqp/compare/2018....9-g22b4b69
MoarVM bump brought: github.com/MoarVM/MoarVM/compare/2...2-gfa0fc18 fa0fc18 Merge branch 'lazier_inline_fixups' 9655e15 we can re-use these spesh slots. 8a5615e get rid of spesh retry mechanism 587e08d Fix fixing of wvals during inline
¦ rakudo: version bump brought these changes: github.com/perl6/nqp/compare/2018....9-g22b4b69
Zoffix releasable6, next 21:10
releasable6 Zoffix, Next release in ≈6 days and ≈21 hours. R6 is down, GitHub is down. At least 0 blockers. Changelog for this release was not started yet
Zoffix, Sorry kid, that's not my department. 21:11
Zoffix AlexDaniel: what's with the bot? That stuff ain't down.
Reminder, release will be in 7 days and there are still 7 release blockers on the list. Please help fix: github.com/rakudo/rakudo/issues?q=...2%9A%A0%22
ZOFVM: Files=1294, Tests=153316, 145 wallclock secs (20.47 usr 3.36 sys + 3057.77 cusr 146.32 csys = 3227.92 CPU) 21:13
Geth rakudo/post-release-2018.04: 6e8dc6f132 | (Zoffix Znet)++ | 2 files
Move .assuming from Block to Code

So it's available in WhateverCodes
Fixes R#1735 github.com/rakudo/rakudo/issues/1735
21:16
synopsebot R#1735 [open]: github.com/rakudo/rakudo/issues/1735 No such method 'assuming' for invocant of type 'WhateverCode'
Geth roast: 9136369a4f | (Zoffix Znet)++ | S02-types/whatever.t
Spec WhateverCode.assuming

Covers R#1735: github.com/rakudo/rakudo/issues/1735 Rakudo fix: github.com/rakudo/rakudo/commit/6e8dc6f132
21:17
Zoffix ugh
Geth roast: 555e1f66b5 | (Zoffix Znet)++ | S02-types/whatever.t
Revert "Spec WhateverCode.assuming"

This reverts commit 9136369a4f73add83efdd83b7925bf54b6e3d6f8.
  (meant to go in post-release branch)
roast/post-release-2018.04: 5bfe416140 | (Zoffix Znet)++ | S02-types/whatever.t
Spec WhateverCode.assuming

Covers R#1735: github.com/rakudo/rakudo/issues/1735 Rakudo fix: github.com/rakudo/rakudo/commit/6e8dc6f132
Zoffix Time to make some toast... 21:20
AlexDaniel: interestingly, p6lert *bot* is leaking even faster than the web app (it's at 1200MB vs 1012MB for the app), yet the other bots, like geth, don't seem to be leaking 21:24
ahh, it has its own perl6 21:25
2017.12-58-g418fc068f for p6lert vs 2018.03-148-g916b41a21 for geth
.seen jnthn 21:38
yoleaux I saw jnthn 14:46Z in #moarvm: <jnthn> Can't say I've noticed it doing so, but I've hardly run spectest at all in the last couple of weeks.
Zoffix looks at the blockers and ponders our bus factor :}
The big-endian stuff... Do you actually have to have a big ending CPU or can that be emulated in a VM or something? 21:39
TIL big/little-endian is about which end to crack a boiled egg to eat it... 21:40
geekosaur it can be emulated but software only except on one of the CPU archs that can switch (mips, ppc, arm iirc) 21:41
Zoffix aye google-fu tells me I can use QEMU to do that 21:48
2018.03 toast finished. So, it takes 70-minutes per commit to run it (on 64-cores) 22:31
m: say 4*70/64
camelia 4.375
Zoffix m: say (64/4)*70 22:32
camelia 1120
Zoffix m: say (64/4)*70/60
camelia 18.666667
Zoffix or 18⅔ hours on 4-core box 22:33
buggable: toast 23:41
buggable Zoffix, Between 2018.03-234-g72b54dd and 2018.03: 13 (1.28%) modules got burnt; 17 (1.67%) got unsucced; 288 (28.26%) out of 1019 modules appear unusable. See toast.perl6.party/ for details.
Zoffix Looks like a bunch of them are just tests that rely on our old buggy num stringification 23:42
timotimo mhm 23:44
Method 'iterator' must be implemented by Iterable because it is required by roles: Iterable. 23:45
this is about punning Iterable accidentally? 23:46
# expected: 'six point zero two two times ten to the twenty-third' 23:47
# got: 'six point zero two two zero zero zero zero zero zero zero zero zero zero zero one times ten to the twenty-third'
Zoffix That too is a num thing
timotimo yep 23:48
just looks very funny
Zoffix :)