00:17 evalable6 left, linkable6 left 00:18 linkable6 joined 00:19 evalable6 joined 00:21 melezhik joined
melezhik I am thinking about creating automated tests system based on active rakudo issues ... 00:23
the idea us
the idea is to have code examples based on users input in issues 00:24
and run them by cron for every new rakudo commit 00:25
so that to make it sure that all active release issues are covered and addressed
initial code samples could be created using RakuPlay web ui, user just need to name builds after issue numbers 00:27
00:27 Kaiepi left
melezhik I already created some examples for some existing issues 00:28
in the end it's possible to have a summary page referencing all closed/active issues as well as RakuPlay builds 00:29
just would like to have an informal feedback here before starting to implement anything 00:30
I know thing like Roast already exists but this might be more tied to issues in a current release ... 00:31
and users not necessarily have to write a unit test for an issue 00:33
this alternative might be just easier for them and take a less efforts ... just drop some code and cron will run it for all new commits 00:34
thoughts? positive criticism? )))) 00:35
timotimo i remember we went through everything that was ever evaluated in camelia or evalable 00:36
melezhik everything? 00:37
00:41 melezhik left 00:47 Kaiepi joined 00:48 melezhik joined
melezhik as an example - rakudist.raku.org/sparky/report/RakuPlay-3/1555 00:48
cron would rerun this build for every new commit till it is green and and the related issue is open 00:50
00:51 melezhik left 01:59 lucasb left
Geth rakudo: vrurg++ created pull request #4076:
Make defined lists not ACCEPTing undefined
roast: vrurg++ created pull request #706:
Change the meaning of List ~~ List.new test
06:27 Altai-man joined 07:34 domidumont joined
[Tux] Rakudo v2020.11-57-g4e21adab9 (v6.d) on MoarVM 2020.11-47-g1c7358004
csv-ip5xs0.804 - 0.826
csv-ip5xs-207.742 - 7.990
csv-parser24.638 - 24.913
csv-test-xs-200.387 - 0.398
test7.631 - 7.706
test-t1.831 - 1.874
test-t --race0.832 - 0.841
test-t-2031.534 - 32.013
test-t-20 --race8.950 - 9.000
08:07 domidumont left 08:08 domidumont joined 08:12 sena_kun joined 08:13 Xliff joined, Altai-man left 08:43 domidumont left 08:52 patrickb joined 08:56 domidumont joined 10:04 lizmat_ joined 10:08 lizmat left, lizmat_ left 10:14 lizmat joined
Geth rakudo: 9fd79f9e8f | (Vadim Belman)++ | src/core.c/List.pm6
Make defined lists not ACCEPTing undefined

So, `List ~~ ()` will be False.
Doesn't break the solution for #1833 because no warning is produced by the above smartmatch.
linkable6 RAKUDO#1833 [closed]: github.com/rakudo/rakudo/issues/1833 [tests needed] Spurious warning when smartmatching Slip ~~ Empty
Geth rakudo: 3d8e942f07 | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | src/core.c/List.pm6
Merge pull request #4076 from vrurg/rakudo_3917

Make defined lists not ACCEPTing undefined
sena_kun m: () ~~ List 10:25
camelia ( no output )
sena_kun m: say () ~~ List
camelia True
sena_kun m: say List ~~ ()
camelia True
sena_kun releasable6, status
releasable6 sena_kun, Next release in ≈19 days and ≈8 hours. 1 blocker. 0 out of 57 commits logged
sena_kun, Details: gist.github.com/2d32aeec537e069bcd...bf44bff9ab
12:11 Altai-man joined 12:14 sena_kun left
lizmat notable6: weekly 13:53
notable6 lizmat, 1 note: 2020-11-27T10:56:13Z <Xliff>: gist.github.com/Xliff/3290a3f31a3f...bb1d4e0480
timotimo releasable6: status 13:56
releasable6 timotimo, Next release in ≈19 days and ≈5 hours. 1 blocker. 0 out of 59 commits logged
timotimo, Details: gist.github.com/13f823a102ec2f298a...740ad7e198
lizmat notable6: weekly reset 13:57
notable6 lizmat, Moved existing notes to “weekly_2020-11-30T13:57:03Z”
14:04 lucasb joined 14:25 leont joined
Geth roast: 44063d0650 | (Vadim Belman)++ | S32-basics/warn.t
Change the meaning of List ~~ List.new test

The smartmatch should return `False`. But the problem it supposed to test for, as stated in rakudo/rakudo#1833, is to make sure no warning is produced by the match. This job is still done well by the test.
roast: 49fb94bf6e | (Vadim Belman)++ | S32-basics/warn.t
Silince down and improve reliability of warning tests

First of all, intercept the warning and don't let them escape to keep TAP output clear.
Also, make sure that the warnings produced are the ones we expect for.
linkable6 RAKUDO#1833 [closed]: github.com/rakudo/rakudo/issues/1833 [tests needed] Spurious warning when smartmatching Slip ~~ Empty
roast: 5256c6958c | (Vadim Belman)++ (committed using GitHub Web editor) | S32-basics/warn.t
Merge pull request #706 from vrurg/rakudo_3917

Change the meaning of List ~~ List.new test
rakudo: lizmat self-assigned inescapable 'Redeclaration of symbol' warnings in the REPL github.com/rakudo/rakudo/issues/4077
e8ab5272f2 | (Elizabeth Mattijsen)++ | src/core.c/REPL.pm6

Fixes #4077. Any output on STDERR will now also cause a "reset" in the sense that it won't combine the previous lines into a single EVAL, as that most likely indicated a "worry" warning (such as described in the issue) or some explicit output on STDERR (such as a "note").
This means that the redeclaration warning will be shown once. Which I think would actually be a nice additional feature.
Altai-man lizmat, not sure if we make it into weekly, but a new Comma release will be announced very soon. 15:40
In minutes.
lizmat then that most likely will be in time :-)
patrickb lizmat: Do you think a call for companies using Raku (to be placed on raku.org) fits into the weekly? 15:50
lizmat yes, if we have a page describing why we would like to know, and where people could give their ok ? 15:51
patrickb lizmat: Hm. Good points. I'll create an issue for raku.org. How much time do I have left? 15:53
lizmat I'd like to be done in an hour or so... 15:54
and I'd rather have this done properly then in a hurry, so I wouldn't mind this being mentioned in next weeks RWN
15:55 vrurg_ joined
patrickb lizmat: OK. Fine with me. 15:55
15:56 vrurg left
[Coke] is it true that we still consider 'ecosystem' to be a stopgap until we get something more CPAN like? 15:57
(doing a slight cleanup on the README and that stands out as possibly archaic at this point)
lizmat I guess... there was talk of a zeco in a grant proposal once?
15:58 vrurg_ left 16:00 vrurg joined 16:01 patrickb36 joined
patrickb36 Coke: I think it's kind of a hot topic. Everyone agrees eco has problems. The controversial question is how to proceed. 16:01
[Coke] OK 16:02
16:02 patrickb left
Altai-man lizmat, twitter.com/koto_san_kana/status/1...8933295107 16:03
patrickb36 I still hope tony-o to gives his proposal another try. I'd love to give him a heads up, but have no idea of how to reach him. 16:04
16:12 sena_kun joined 16:13 Altai-man left 16:18 patrickb36 left 16:23 patrickb joined 16:24 melezhik joined
melezhik Hi rakudo devs , I still hope to get a feedback on my issue/testing idea ... :] 16:26
16:33 cognominal joined
[Coke] Is there a writeup? 16:34
or just here in chat?
melezhik [Coke] are you talking to me? sorry sometimes I lose a context in irc ... ))) 16:36
[Coke] yes, your request just now for feedback. 16:38
melezhik yeah, just wanted to clarify ... so it's just what I've put in chat here before ... I could do some writeup, if more details are needed ... 16:40
just decided to start with some thoughts I dropped here ... without any formal docs ... 16:41
16:45 melezhik left
[Coke] for me, having an issue or something to comment on makes it easier. for some, irc is fine. your mileage will vary 17:19
17:27 melezhik joined
melezhik yeah, [Coke] I could create an issue in github.com/Raku/problem-solving with proposal details ... 17:28
17:37 melezhik left
lizmat And yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2020/11/30/2020-...on-fosdem/ 17:46
moritz lizmat++ 18:07
sjn yay! lizmat++
linkable6 RAKUDO#4077 [closed]: github.com/rakudo/rakudo/issues/4077 inescapable 'Redeclaration of symbol' warnings in the REPL
18:25 domidumont left 18:35 moray joined, moray is now known as morayj
lizmat afk& 19:31
19:42 morayj left 20:12 Altai-man joined 20:13 sena_kun left
timotimo i wonder why the stagestats output makes a difference between stage parse and all other stages 20:34
MasterDuke what do you mean? 20:35
timotimo github.com/Raku/nqp/blob/master/sr...r.nqp#L513 - and one more line further up
MasterDuke huh 20:40
timotimo welp, i'll go slap myself in the face then 20:41
oh, right, because nested compilation happens between the start and end of a stage 20:42
gist.github.com/timo/401de473e1e77...cb53410c89 20:43
i would like it to be a bit more parse-able 20:44
MasterDuke it's verbose
timotimo very
as long as the start and end of stages are being printed out at the start and end of the stage, it'll have to look like this 20:45
no not like this
MasterDuke stick the 'finish in ...' line on the end of the 'started' line if nothing happened inbetween?
timotimo hmm, the "started" line writes a newline unconditionally, though 20:48
should the newline go before the started line instead? 20:49
MasterDuke store the data in a hash and have a env variable (or command line option) for output format, like the json exceptions
timotimo this is supposed to work with multiple processes without having the parent processes read from their children and write to their own output again 20:50
MasterDuke ah
timotimo in particular, the stagestats flag now lets you specify a file path, which can be a fifo for example 20:51
MasterDuke then does it work if you put the newline first?
timotimo let's see 20:55
i'm looking for a good spot in the parser to report parse progress 20:57
i want something that doesn't run too often, so the overhead is minimized 20:58
MasterDuke that looks better. any way to indent the different sets or something like that? 21:12
timotimo not so sure 21:13
i need a different piece of code than the core setting that's big 21:18
especially one that pulls in other long-to-compile files
time for gtk i guess
dang, this example code i had in my backlog just precomped a single file 21:31
21:33 lucasb left
timotimo i'll drop this for now 21:41
21:48 Altai-man left 22:13 patrickb left