01:28 guifa left 03:18 lizmat left 05:30 guifa joined 06:36 guifa left 07:31 [Coke] left 08:52 sena_kun joined 09:11 lizmat joined 09:26 [Coke] joined 10:20 sena_kun left 13:12 guifa joined 16:09 sena_kun joined 17:01 guifa left 17:02 guifa joined 19:32 guifa left 20:02 guifa joined 20:19 sena_kun left 21:13 guifa left
Geth MoarVM/unhandled_target_type_error_message_details: 8865659a00 | (Timo Paulssen)++ | src/core/nativecall.c
in nativecast, output more details

This helped diagnose rakudobug 5682
21:30
timo ok cool geth is reporting pushes, i wonder why it didn't have the one the other day 21:31
i'm not at the computer where i'm logged in to github (because the cat has my chair) so i can't make a pull request right now, but if someone wants to review the change, it's quite small. the branch could be merged IMO 21:32
Geth MoarVM/main: fa5bfd9264 | (Timo Paulssen)++ | azure-pipelines.yml
Port over "cache devshell dll location" from rakudo CI
21:48
timo oops that was meant to be in a branch ... huh 21:49
Nicholas blame the cat? 21:50
timo yes that is exactly what happened! 21:51
Nicholas :-)
Geth MoarVM/faster_dev_powershell_in_azure_pipelines: 1beaf49e2f | (Timo Paulssen)++ | azure-pipelines.yml
Fix OS-is-windows check that doesn't work in this file
timo is there a way to prevent pushes to main, but only from me? :D 21:52
aw crud, non-main-branch commits don't get azure runs? 21:53
i guess i don't have to sit down to click a few things
Geth MoarVM: timo++ created pull request #1883:
azure CI improvements taken from the recent rakudo CI re-imagining
21:54
ab5tract timo: IIUC you should only need to create a (draft) PR for the azure runs
Nicholas prevent pushes - it's certainly possible on gitlab, but I don't know exactly how there, let alone where to look on github for something similar
no idea about the Azure thing
timo yeah, can't make one without being logged into github though
yeah gitlab and github both have "protected branches". not sure if the rule "only disallow timo" would be something you can configure in either?
Nicholas your cat needs to watch more Bond films - the human is supposed to be *between* the cat and the chair
"Problem Exists Between Cat And Chair" 21:55
timo :D
Nicholas I assume that it's technically possible to make everyone the "admin who can push to main" apart from timo's cat's staff 21:56
Geth MoarVM/faster_dev_powershell_in_azure_pipelines: 092232206e | (Timo Paulssen)++ | azure-pipelines.yml
aaaaand a typo
timo yeah but of course i would become sad if i lose all the other privileges that come with being an admin on a github repo :)
21:57
The macOS-12 environment is deprecated, consider switching to macOS-13, macOS-14 (macos-latest) or macOS-15. For more details, see github.com/actions/runner-images/issues/10721
^- also something we should put into the moar CI, but that's also easy enough
a thingie that runs clang's scan-build and gcc's -fanalyzer would be neat, too. 21:58
ummm have we always had the "Build NQP" step attempt to run PWSH code on mac because mac is not linux? 22:03
Nicholas This is a sensible question and I have no idea about the answer. (Sorry) 22:04
timo :D
Geth MoarVM/faster_dev_powershell_in_azure_pipelines: df017973f4 | (Timo Paulssen)++ | azure-pipelines.yml
Switch "linux" vs "non-linux" to "windows" vs "non-windows"

The code for mac should be the same as linux, not the same as windows. We do not use powershell nor Visual Studio on mac.
22:07
Nicholas I need to go to bed. Don't stay up too late. 22:08
timo haha 22:15
Geth MoarVM/faster_dev_powershell_in_azure_pipelines: 370eff49aa | (Timo Paulssen)++ | azure-pipelines.yml
don't error out if catchsegv doesn't exist (like on mac)
22:19
timo looks like i might have to wait extra-long this time around for the windows builds to even consider starting 22:20
why am i doing azure pipelines to myself again 22:34
azure has decided that the best order to run the 22 jobs in is first 20 jobs i am not interested in seeing, then the two i want at the very end. 22:37
one of them has finally started 22:38
22:40 lizmat left
timo so, push commit introducing caching, wait 19 minutes for the first windows build to start, wait about 9 minutes for the "find dev shell dll" process to finish, then another however-many minutes for the entire build and tests to finish. after all that - and not earlier, because github would cancel the pipeline build, then you don't get anything in the caches at all - push another change to see if 22:41
the caching is loaded properly, wait 19 minutes again for the first windows job to start, and then you may find out if it works or not. if it doesn't work, start from step one.
[Coke] ugh 22:52
thanks for slogging through it
timo yep. i got it wrong. haha. fun. 22:57
i did notice it before it ran to completion
i'll see what happens if i cancel the other jobs in the run 22:58
oh i'm not signed in to azure on this computer either, of course 22:59
nope. can't even when signed in. cancel all, or cancel nothing, no in-between 23:01
that's a benefit of the different way i've set it up in the new rakudo implementation, there you can cancel "the mac builds" or "the windows builds" or "the linux builds" 23:02
Geth MoarVM/faster_dev_powershell_in_azure_pipelines: f402efa477 | (Timo Paulssen)++ | azure-pipelines.yml
Use macos-14 by default and -13 for the "old OS" job
23:49
timo ^- no-change commit to cause a new azure pipeline run
oh, i guess i hadn't pushed the commit yet? so it actually *is* a new commit? 23:50