| IRC logs at
Set by AlexDaniel on 12 June 2018.
00:04 vrurg joined 00:36 lucasb left 00:50 AlexDaniel joined 00:51 AlexDaniel left, AlexDaniel joined 01:34 sena_kun left 01:47 sena_kun joined 01:56 Kaiepi left, Kaiepi joined 03:34 sena_kun left 03:39 Geth left 03:48 sena_kun joined 03:59 moon-child left 04:04 moon-child joined 04:40 moritz left, moritz joined 04:53 squashable6 left 04:55 squashable6 joined 05:18 vesper left 05:23 vesper11 joined 05:34 sena_kun left 05:48 sena_kun joined 06:02 jpf1 left 06:03 jpf1 joined 07:33 sena_kun left 07:38 domidumont joined 07:47 sena_kun joined 08:09 patrickb joined 08:20 Ven`` joined 09:04 zakharyas joined 09:06 Voldenet left 09:11 Voldenet joined, Voldenet left, Voldenet joined 09:27 zakharyas left 09:32 zakharyas joined 09:33 sena_kun left 09:46 sena_kun joined 11:17 timotimo left, timotimo joined 11:34 sena_kun left 11:42 squashable6 left 11:45 squashable6 joined 11:47 sena_kun joined 12:30 zakharyas left 12:31 MasterDuke left 13:12 lucasb joined 13:17 Geth joined, rypervenche left 13:21 rypervenche joined 13:24 Ven`` left 13:33 sena_kun left 13:44 zakharyas joined 13:48 sena_kun joined 14:15 AlexDaniel left 15:34 sena_kun left 15:47 sena_kun joined 16:18 patrickb left 16:25 domidumont left 16:29 patrickb joined
patrickb I'm currently looking at the dyncall 3rdparty submodule. Version 1.1 got released recently and I'd like to update. 17:20
When looking at the git history it seems as older updates actually imported the mercurial commits while the two more recent bumps just copied all the files in. 17:21
Does that mean, that there are actually no changes between the official mercurial dyncall repo and the git repo?
Is updating as easy as replacing the entire working directory of the dyncall git repo with the respective mercurial commit and commiting the result (and loosing any potential changes there might possibly have been in our repo)?
jnthn Hopefully any of the changes we did make are long enough ago to have been fixed upstream. The commit log for the repo suggests there are very very few such changes though 17:24
And others may well have just done exactly what you're suggesting since then
I'd try that as a first resort, anyway
patrickb So the plan is to just hope for the best and overwrite with vanilla upstream. OK. Will do! 17:25
17:33 sena_kun left 17:48 sena_kun joined 18:04 zakharyas left
patrickb nine: I have updated and renamed the option to --git-cache-dir. Are you OK with the changes now? 18:32
18:49 camelia left
nine patrickb: yep 18:50
18:56 vrurg left
patrickb May I kindly ask for a merge :-) 18:56
Geth MoarVM: f7a3a5ccdc | (Patrick Böker)++ | 2 files
Implement `--git-cache-dir` option

This option makes the configure process create / update git repositories for all of its submodules in the given folders and use those as reference repos.
MoarVM: ecddb4de5f | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | 2 files
Merge pull request #1228 from patrickbkr/git-reference-option

Implement `--git-reference` option
lizmat patrickb nine ^^
should I bump Moar / NQP ?
patrickb lizmat: Thanks! 19:06
lizmat: A bump would be fine. Then I can also merge the corresponding PRs in NQP and rakudo. :-D 19:07
lizmat ok, will do the bump in Moar then, leaving the NQP and Rakudo ones to you ?
19:31 vrurg joined 19:33 sena_kun left 19:46 sena_kun joined 19:51 zakharyas joined
patrickb Dyncall bump PR is done: 20:42
^ Merge at latest convenience.
The actual bump in MoarVM will happen separately.
lizmat patrickb I would like to merge asap, to give more testing before release 20:44
so, should I merge that now ?
jnthn ?
21:08 zakharyas left 21:11 Kaiepi left 21:12 Kaiepi joined 21:33 sena_kun left 21:48 sena_kun joined
dogbert11 t/spec/S07-hyperrace/basics.t fails one of its tests 21:59
not ok 84 - hyperized s/…/…/;
22:00 MasterDuke joined
lizmat dogbert11: yeah, reported this a few hours ago on #raku-dev, no takers :-( 22:06
MasterDuke looks like it might be that s/// change jnthn made recently 22:07
lizmat builds without that commit 22:09
yup, that's the one 22:11
I wonder if the test is faulty 22:12
MasterDuke in the got: <...>, "++", "", "++", <...> 22:13
Use of Nil in string context in block at t/spec/S07-hyperrace/basics.t line 177 22:14
worker in a parallel iteration (hyper or race) initiated here: in sub _is_deeply at /home/dan/Source/perl6/rakudo/lib/Test.rakumod (Test) line 675 in sub is-deeply at /home/dan/Source/perl6/rakudo/lib/Test.rakumod (Test) line 590 in sub is-deeply at /home/dan/Source/perl6/rakudo/lib/Test.rakumod (Test) line 586 in block <unit> at
t/spec/S07-hyperrace/basics.t line 187Died at: Your printf-style directives specify 0 arguments, but 2 arguments were supplied in block at t/spec/S07-hyperrace/basics.t line 187
looks like a memory corruption or something like that
lizmat well, then we finally have a reproducible case for that :-) 22:15
MasterDuke: will you do the honors of an issue, or should I?
MasterDuke i can 22:17
22:28 Kaiepi left 22:30 Kaeipi joined
lizmat MasterDuke++ 22:32
23:02 lucasb left 23:34 sena_kun left 23:47 sena_kun joined 23:59 Kaeipi left