01:22
MasterDuke joined
|
|||
MasterDuke | timo: seems like something you'd be interested in github.com/dbohdan/memsparkline | 01:26 | |
unrelated, but i just got an mb air and while it builds rakudo 30% faster than my zen2 desktop, there are three failing spectests | 01:28 | ||
t/spec/S16-io/eof.t (Wstat: 256 Tests: 5 Failed: 1) | 01:29 | ||
Failed test: 3 | |||
Non-zero exit status: 1 | |||
t/spec/S32-io/IO-Socket-Async.t (Wstat: 256 Tests: 3 Failed: 1) | |||
Failed test: 2 | |||
Non-zero exit status: 1 | |||
Parse errors: Bad plan. You planned 40 tests but ran 3. | |||
t/spec/S32-io/out-buffering.t (Wstat: 256 Tests: 4 Failed: 1) | 01:30 | ||
Failed test: 4 | |||
Non-zero exit status: 1 | |||
02:29
nine left
02:30
nine joined
03:16
MasterDuke left
04:11
vrurg left
04:23
vrurg joined
|
|||
ab5tract | I definitely recalls seeing that io socket async being a flapper before | 10:14 | |
10:44
sena_kun joined
|
|||
Geth | Text-Caesar/main: 47799b83e1 | (Elizabeth Mattijsen)++ | 26 files CI test in preparation for a Raku Community release |
11:29 | |
bartolin | I see the failures in S16-io/eof.t and S32-io/out-buffering.t on my FreeBSD box as well. I didn't look in detail, but it seems that in both cases an error is reported: "script: tcgetattr/ioctl: Operation not supported\n" | ||
Geth | Text-Caesar/main: 26fff71749 | (Elizabeth Mattijsen)++ | 3 files 0.2 |
11:32 | |
bartolin | Oh, also the tests have been fudged for "Sonoma": github.com/Raku/roast/commit/68705c09fd | 11:34 | |
Geth | Lingua-Conjunction/main: 9b0777f9d1 | (Elizabeth Mattijsen)++ | 10 files 1.2 |
11:56 | |
Lingua-Conjunction/main: 223941eb3c | (Elizabeth Mattijsen)++ | 2 files 1.3 |
|||
Lingua-EN-Conjugate/main: 6a6b35b214 | (Elizabeth Mattijsen)++ | 14 files CI test in preparation for a Raku Community release |
12:33 | ||
Lingua-EN-Conjugate/main: ee01093dea | (Elizabeth Mattijsen)++ | 2 files 0.3 |
12:42 | ||
patrickb | bartolin: Can you create a bug report and ping me in it? | 12:53 | |
lizmat | Geth | 13:11 | |
13:11
Geth left,
Geth joined
|
|||
jdv | smells like a release day | 14:00 | |
lizmat | it does! | 14:24 | |
Geth | Math-Matrix/main: 0efeec5624 | (Elizabeth Mattijsen)++ | 45 files CI test in preparation for a Raku Community release |
14:43 | |
jdv | what is the deal with the blin results?... | 14:44 | |
[Coke]: around? | |||
Geth | Math-Matrix/main: 3c130477bb | (Elizabeth Mattijsen)++ | 5 files Make sure dependencies get installed in CI |
14:47 | |
Math-Matrix/main: 2ed07ee56e | (Elizabeth Mattijsen)++ | 5 files 0.4.1 |
14:54 | ||
jdv | lizmat: any idea what's going on with the 2nd blin ticket? | 15:11 | |
curious its not marked as a blocker. mistake or on purpose? | 15:12 | ||
lizmat | afaik all issues were fixed? | ||
jdv | ok, done with that | 15:15 | |
lizmat | Text::CodeProcessing needs to be fixed by the author antononcube | ||
jdv | cool. just freshening the changelogs now =. | 15:18 | |
lizmat: done with changelogs if you want to look. was just a handful added. | 15:27 | ||
Geth | Dice-Roller/main: 786916330c | (Elizabeth Mattijsen)++ | 21 files CI test in preparation for a Raku Community release |
15:29 | |
[Coke] | jdv: here now | 15:30 | |
looks like you already got there. | |||
jdv | wherever there is, sure:) | ||
Geth | Dice-Roller/main: e7d4e5bff9 | (Elizabeth Mattijsen)++ | 2 files 0.1.2 |
15:31 | |
jdv | all i've done so far is close out the blockers - just the 2 blin tickets, and updated the moarvm and rakudo changelogs | ||
Geth | Unicode-UTF8-parser/main: 50fb7ae0a8 | (Elizabeth Mattijsen)++ | 3 files 0.3 |
15:33 | |
lizmat looks at the Rakudo changelog | 15:38 | ||
jdv: looks good | 15:40 | ||
jdv | thanks | 15:41 | |
[Coke]: what do you want to do? | 15:59 | ||
[Coke] | I just wanted to make sure there was backup, I didn't necessarily need to press any buttons todya | 16:04 | |
we now have working blin backup (yay), I have the keys needed to sign releases... | 16:05 | ||
jdv | do you have commit bits for all the repos | 16:07 | |
do you have your pgp fingerprint in your gh profile like me and patrickb? | 16:08 | ||
[Coke] | Yes - was able to sign one of my releases: here; | ||
jdv | spectest is clean for me atm, installed ake and Cro::HTTP::Client which i remember i need somewhere in this process | ||
[Coke] | github.com/coke/raku-cal/releases/tag/2024.12 | 16:09 | |
jdv | i believe i updated the 2 release guides well enough but i haven't tried to use them without my notes so not sure | 16:10 | |
did infra add your ssh key to the boxes it needs to be on? | |||
how about i do the release today and you do the next one if you feel comfortable then or the one after that...? | 16:13 | ||
[Coke] | I did NOT interact with infra. Yah, why don't you do it today, and I'll plan for january? | 16:14 | |
jdv | and then after you get a release out we can get patrickb onboard next | ||
[Coke] | I can do a test run without pushing near new year. | ||
jdv | well, part of this release is picking a date for the next so you tell me:) | 16:15 | |
coleman: can we get [Coke]'s ssh key setup for doing a release? | 16:16 | ||
coleman | yes. post the PUBLIC key to an issue in Raku/infra | 16:21 | |
[Coke] | Jan-27 | 16:22 | |
? | |||
jdv | friday is good for you? | ||
[Coke] | or is it normally earlier? can do a week earlier also | ||
No, I have $dayjob | |||
jdv | oh, i was looking at december | 16:23 | |
jan 27 is a monday, right? | |||
2025-01-25 is a Sat. is that what you mean?:) | 16:25 | ||
[Coke] | coleman: done | 16:26 | |
... I did mean saturday. wtf. | |||
ah, was looking at `cal 1 2024` :sigh* | 16:27 | ||
yes, 18 or 25 both work | |||
jdv | five and twenty it is then | 16:35 | |
Geth | rakudo/release-2024.12: a006a3d1d7 | (Justin DeVuyst)++ | 3 files Update changelog + announcement Deliberately not logged: [e8efeccd][450d5486][50345ec8][f2e5f2c4][02910e43][2053ea98] [93baf309][4e051c5b][fd29555b][48d3e2ce][df2ae397][b6a72ac4] [fa72e6be][0db7149f][ba84cd99][167d1dd9][238e313e][b1f741f3] [7d29c62a][2147e6b8][24a1cdbb][1ff7f085][c632dd77][461b81f7] [530e2059][dd45859f][936c3569][10397f16][998fccfb][42675f13] [9bf3be4d][a01021a9][4082d2c7][7e5e210f][22a5b0ec] |
16:59 | |
jdv | got the first bits of the rakudo side done. added a missing step to the release guide. | ||
now on to the moarvm part | |||
moarvm release done with slight hiccup. see #moarvm. Back onto the back half of this one. | 17:42 | ||
Geth | roast/6.c-errata: d2c991bc8d | (Elizabeth Mattijsen)++ (committed by Justin DeVuyst) | S02-types/lists.t Fix tests in light of #3658 See github.com/rakudo/rakudo/commit/a4b87c9186 |
18:40 | |
roast/6.c-errata: 1110595a10 | (Elizabeth Mattijsen)++ (committed by Justin DeVuyst) | S02-types/lists.t Fix copy-pasto |
|||
jdv | found and fixed the single 6.c-errata test failure | 18:42 | |
just a cherry pick from master | |||
lizmat | jdv++ | ||
jdv | lizmat: uh, looks like a 6.d-errata test fail involving polymod that i don't see a master change for | 18:59 | |
MISC/bug-coverage-stress.t | |||
lizmat checks | |||
jdv | gist.github.com/jdv/7cb44a39b92e37...93f339c422 | ||
lizmat | still looking | 19:03 | |
jdv | no rush. i'm fixing others:) | ||
lizmat | 2346529e636717adde would be the one in master | 19:04 | |
linkable6 | (2024-12-06) github.com/Raku/roast/commit/2346529e63 Fix stress test that used .polymod | ||
Geth | roast/6.d-errata: b11b6d1882 | (Elizabeth Mattijsen)++ (committed by Justin DeVuyst) | S02-types/lists.t Fix tests in light of #3658 See github.com/rakudo/rakudo/commit/a4b87c9186 |
19:07 | |
roast/6.d-errata: 0cc0430535 | (Elizabeth Mattijsen)++ (committed by Justin DeVuyst) | S02-types/lists.t Fix copy-pasto |
|||
roast/6.d-errata: 88ecd1ca92 | (Elizabeth Mattijsen)++ (committed by Justin DeVuyst) | S32-num/polymod.t Fix polymod test In light of github.com/rakudo/rakudo/commit/818a543a4e |
|||
jdv | that's all the others i fouund | 19:08 | |
lizmat | testing a fix | ||
Geth | roast/6.d-errata: 8134fd301a | (Elizabeth Mattijsen)++ | MISC/bug-coverage-stress.t Re-apply 2346529e636717 from master |
19:09 | |
lizmat | that should be it | 19:10 | |
jdv | thanks | 19:11 | |
i think we're back on track, re-errata testing just for fun | 19:12 | ||
clean runs | 19:24 | ||
where does the version string come from again? | 19:37 | ||
lizmat has no idea | |||
jdv | for some reason my newly built rakudo says "Welcome to Rakudo™ v2024.10-101-g03844dc7d." which should be v2024.12 | 19:38 | |
what is happening?! | |||
who knows about this stuff? this is a first for me | 19:56 | ||
its the correct commit but its the wrong ref in the version its spitting out | |||
ah, nevermind. the release guide and i parted ways it seems. i'll fix it later. | 19:59 | ||
back on track | |||
jdv is losin' it | |||
ab5tract | jdv++ | 20:07 | |
Geth | nqp/main: 30ffbb7869 | (Justin DeVuyst)++ | tools/templates/MOAR_REVISION [release] Bump MoarVM revision to 2024.12 |
20:12 | |
nqp/main: 5a123cbd2f | (Justin DeVuyst)++ | VERSION [release] Bump VERSION to 2024.12 |
|||
rakudo/release-2024.12: 019347b7b7 | (Justin DeVuyst)++ | tools/templates/NQP_REVISION [release] Bump NQP revision to 2024.12 |
|||
rakudo/release-2024.12: 03844dc7dc | (Justin DeVuyst)++ | VERSION [release] Bump VERSION to 2024.12 |
|||
rakudo: jdv++ created pull request #5731: Release 2024.12 |
20:14 | ||
rakudo/main: 4 commits pushed by (Justin DeVuyst)++ | 20:15 | ||
jdv | .tell patrickb the 2024.12 release happened | 20:28 | |
is the bot not here? | |||
patrickb: the 2024.12 release happened | |||
idk how else to tell El_Che but the bot:( | 20:29 | ||
release is done. commit away. thanks all! | |||
[Coke]: and that's a release, i guess:) | |||
anyone know who runs the bot that handles ".tell"? | 20:30 | ||
i emailed El_Che though | 20:32 | ||
timo | that's the *ables bots | 20:44 | |
notable6: help | |||
notable6 | timo, Like this: notable6: weekly rakudo is now 10x as fast # See wiki for more examples: github.com/Raku/whateverable/wiki/Notable | ||
timo | not this one | ||
tellable6 has disconnected some time ago? | 20:46 | ||
patrickb | jdv: Also one should put the gpg key here: github.com/rakudo/rakudo.org/tree/...ublic/keys | 20:49 | |
and here: github.com/rakudo/rakudo.org/blob/...tml.ep#L37 | 20:50 | ||
bartolin | patrickb: I hope I'll come around to create an issue for the test failures tomorrow. From what I've seen so far, those two tests are the only ones that use run-with-tty (github.com/Raku/roast/blob/c2d2875...umod#L382) | 21:59 | |
I think that the error can be shortened to the following: ./rakudo-m 'my $f = "foo"; $f.IO.spurt: "say 42"; my $proc = shell(:in, :err, "script -q /dev/null \"$*EXECUTABLE.absolute()\" \"$f\""); $proc.in.spurt("\n", :close); say $proc.err.slurp(:close)' | |||
> script: tcgetattr/ioctl: Operation not supported | 22:00 | ||
I might be wrong, but it looks like this is the source of the error: cgit.freebsd.org/src/tree/usr.bin/...le/14#n222 | 22:01 | ||
(and my command missed the -e at the start) | |||
Geth | rakudo/main: 70c268ba43 | (Christian Bartolomäus)++ (committed using GitHub Web editor) | src/Raku/ast/signature.rakumod Only call ensure-sc if there is a descriptor On the JVM backend this avoids a NullPointerException for the following code: Format.new("%5s") ... (6 more lines) |
22:30 | |
rakudo/main: 7ef44ef5ee | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | 3 files Add VM.ownup to produce backtraces of all threads and exit This wraps Timo Paulssen's new "all-thread-bt" MoarVM syscall in a method on the VM class, and attempts to do the same on other backends. That syscall generates a complete backtrace of *all* running threads ... (9 more lines) |
22:31 | ||
rakudo/main: 4aa8d331aa | (Christian Bartolomäus)++ (committed using GitHub Web editor) | 2 files Move test file that dies on JVM to t/09-moar This is really just a bandaid to make "make test" usable again. The test doesn't work on the JVM backend: Even if I replace the usage of atomicint with a plain int, there is a compile time error: Type check failed for return value; expected Mu but got BASE (BASE) As noted in the leading comment of the test file, the final destination of the test should be roast, anyway. So hopefully moving it to t/09-moar is good enough for now. |
22:32 | ||
rakudo/main: 87f0e37f54 | (Will Coleda)++ (committed using GitHub Web editor) | 2 files Remove playful "just yet" in error messages It's not explicitly checked for in test/spectest |
22:36 | ||
rakudo/main: 24b4001e63 | ab5tract++ (committed using GitHub Web editor) | 2 files Provide adverbial forms of map This commit opens a different way of specifying map variants. This is mostly for cosmetic reasons and operates under the impression that named argument adverbs, had they been available, would have been used over the smashedcase versions we currently offer. * [flatmap](github.com/Raku/problem-solving/issues/430) |
22:38 | ||
22:41
sena_kun left
|
|||
coleman | [Coke] and jdv : you can test the ssh permissions now github.com/Raku/infra/issues/59#is...2543369319 | 23:02 | |
ugexe | why ownup instead of own-up? | 23:22 | |
Geth | rakudo/lower-bound-for-revision-gating: 01398190fe | ab5tract++ | 3 files Add lower-bounding for the revision-gated trait This adds a finishing touch to revision gating: the ability to use revision gating to evolve methods that otherwise have the exact same signature. The is done by adding the trait to the candidate that is to be replaced: ... (23 more lines) |
23:38 | |
ab5tract | surprised to see the map adverbs merged | 23:44 | |
I already had an improvement in mind, which is to pass the map block as the named parameter directly | 23:46 | ||
Geth | rakudo/main: 720cd014c8 | ab5tract++ | 2 files Revise adverbial map forms to be more direct Directly passing the block via the named arguments feels more fluent: [1,[1,[1,1,[2,2]]]].map: deep => * + 1 # [2, [2, [2, 2, [3, 3]]]] "okokokok".comb.rotor(2).map: :flat(*.reverse) # (k o k o k o k o) |
23:54 |