github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
nwc10 good *, #moarvm 09:02
(I forgot)
jnthn releasable6: status 09:16
releasable6 jnthn, Next release in ≈25 days and ≈9 hours. There are no known blockers. Changelog for this release was not started yet 09:17
jnthn, Details: gist.github.com/8b30ad8b34323fc920...46d0c95692
jnthn I think that means we can merge the hash stuff rather soon :)
nwc10 ah yes
I realised that I was a bit fried yesterady, so didn't try to prepare for this
my plan was
make a branch A-Better-Hash
fix that XXX commit message
and, maybe
re-order the code review commits immediately after their relevant first commit(s), and verify that `git diff` between the two branches is 0 09:18
I'm notionally doing $work currently
but I shouldn't summarise that on a logged channel. 09:19
MasterDuke nwc10: would you squash/rebase the code review commits into their relevant first commits or leave them separate? 09:39
nwc10 if I put them next to them, I think I'd prefer to leave them separate 09:40
I see some merit in leaving the history of "ideas we explored but didn't quite get right first time" 09:41
but "next to them" also then means that it's not too hard to see what we ended up with
anyway, I have a work ticekt to work on 09:42
which obviously means that I can now charge tea drinking to another department :-)
jnthn: rakuast doesn't generate any ASAN excitement (did not run spec tests) 10:18
but IIRC new-disp did at some point about the time you went on holiday. but as the spectests have (I think) moved on and it has not, I didn't run them 10:19
and I can't currently spot what I thought was upsetting it
dogbert11 libuv 1.39 is out, github.com/libuv/libuv/blob/v1.x/ChangeLog 11:07
jnthn Looks fairly low risk, and good timing for us to bump 11:09
nwc10 good *, brrt 12:31
or is that just good *, brrt's client? 12:32
brrt good * nwc10 12:39
Geth MoarVM: dogbert17++ created pull request #1339:
Update libuv to v1.39.0		 14:22
jnthn dogbert11: Hmm, CI sees a Windows test failure 14:48
MasterDuke NMAKE : fatal error U1073: don't know how to make 'gen/nqp-version' 14:56
dogbert11 MasterDuke: is that all it says? 15:58
this change is slightly suspect: * build,win: link to user32.lib and advapi32.lib (George Zhao) 16:01
dogbert11 how do I even know that libuv had anything to do with this 18:19
is it possible to rerun this part somehow? 18:20
timotimo perhaps make a pullrequest with only that commit reverted? 18:58
Altai-man timotimo, why? 19:08
After re-run CI passed. 19:09
timotimo damn
[Coke] Altai-man: adapated your PR comments after it got merged to master; thanks. 19:11
... wrong window.
Altai-man [Coke], you are welcome! Thanks for your improvements in the first place. :) 19:14
dogbert11 yay, Altai-man, did you rerun the the CI test? 20:24
jnthn: the test failure disappeared after the failing test was rerun 20:27
Altai-man dogbert11, yeah. 20:34
jnthn dogbert11: ah, ok, nice 21:00
Maybe unlucky timing with respect to some other nqp/rakudo change
Geth MoarVM: 29ce8171f7 | (Jan-Olof Hendig)++ | 3rdparty/libuv
Update libuv to v1.39.0

Spectest clean under Linux Mint (Ulyana) 64-bit		 21:10
MoarVM: 15a76dcb3e | (Jonathan Worthington)++ (committed using GitHub Web editor) | 3rdparty/libuv
Merge pull request #1339 from dogbert17/update-libuv-2-v1.39.0

Update libuv to v1.39.0
lizmat will someone bump nqp and Rakudo ? 21:14
or should I?
jnthn lizmat: go for it, if you didn't already 22:27

Powered by Cro and the Raku® Programming Language.

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

Thank you!