lizmat Files=1337, Tests=114215, 224 wallclock secs (29.38 usr 8.26 sys + 3092.12 cusr 303.38 csys = 3433.14 CPU) 09:07
Geth_ rakudo: AntonOks++ created pull request #4006:
make the offered rakudo-moar-$VERSION-$REVISION-win-x86_64.zip file consistent with the included compressed directory name		 11:31
MasterDuke lizmat++ hope i wasn't being pushy 11:35
lizmat MasterDuke: no, you made valid points and the resulting PR is better for it 11:36
MasterDuke cool 11:40
[Coke] dumb nit: I'd replace ... with … 15:07
but in general, seems fine. +1 for merging. 15:08
[Coke] is now curious how coverage testing works at all. :) 15:09
vrurg_ got a situation where a callback is invoked with wrong closure. oops... 15:14
vrurg Wish I have an idea how to golf it down. 15:15
[Coke] when in doubt, start commenting out code and put it back when it starts working. (I've done this the hard way a few times to try to reduce the amount of code needed to trigger something.) 15:18
and maybe in the process you can see the shape of the thing that is causing the error. 15:19
vrurg [Coke]: Let me paraphrase it: wish I know a shorter way. ;) 15:26
[Coke] :)
How big is the whole code base?
vrurg It's rather small, 300-400 lines. It's a re-write of Async::Workers. 15:28
Yet, I've already spent so much on his re-write, that want to be over with it ASAP. :( 15:29
lizmat bisectable6: say "REGIONAL INDICATOR SYMBOL LETTER A".uniparse.NFD 16:58
bisectable6 lizmat, Will bisect the whole range automagically because no endpoints were provided, hang tight
tellable6 2020-11-05T15:33:31Z #raku <melezhik> lizmat rakudist.raku.org/sparky/report/debian/897
2020-11-05T16:41:07Z #raku <melezhik> lizmat you can use Rakudist to test your github repos if it helps
bisectable6 lizmat, Output on all releases: gist.github.com/4559a19cdb2cddd47f...1c837b85ae
lizmat, Bisecting by exit code (old=2017.12 new=2018.01). Old exit code: 1
lizmat, bisect log: gist.github.com/afea5bc28c16f2aee5...9168c3c5c9 16:59
lizmat, (2017-12-21) github.com/rakudo/rakudo/commit/2a...bac170da01
lizmat, Bisecting by output (old=2016.09 new=2016.10) because on both starting points the exit code is 1
lizmat, bisect log: gist.github.com/05949f3d82007ae195...df36dd5705
lizmat, (2016-09-27) github.com/rakudo/rakudo/commit/22...0f14b9c05c
lizmat, Output on all releases and bisected commits: gist.github.com/1038df9d24c7ffa0a4...e2e82b33eb
vrurg Altai-man: are you still around? 19:37
Altai-man vrurg, yeah 19:41
vrurg Ok, ignore the question in the ticket. :) How do you run blin against a branch in the main repo? 19:42
--new didn't work for me.
Altai-man vrurg, hm, using `--new`. "Didn't work" as when?
vrurg The day I merged into the branch. 19:43
Ok, it was too early, perhaps. Looks as it started now. 19:44
Altai-man Great. I can do a run if needed.
vrurg Nevermind, should be fine now. Minor glitches like missing zstd or locked dir, but should be fine. 19:47
Altai-man have fun
vrurg 👍🏻 19:48
Thanks. :)
sena_kun Anyone who is good with JS and has some free hours available, wanting to contribute greatly by writing a hundred or two lines of code? :) 21:18

Powered by Cro and the Raku® Programming Language.

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

Thank you!