Welcome to the main channel on the development of MoarVM, a virtual machine for NQP and Rakudo (moarvm.org). This channel is being logged for historical purposes.
Set by lizmat on 24 May 2021.
00:00 reportable6 left 00:02 reportable6 joined 01:02 shareable6 left, statisfiable6 left, bloatable6 left, squashable6 left, greppable6 left, tellable6 left, reportable6 left, linkable6 left, coverable6 left, committable6 left, notable6 left, nativecallable6 left, benchable6 left, releasable6 left, bisectable6 left, unicodable6 left, quotable6 left, sourceable6 left, evalable6 left, quotable6 joined, greppable6 joined, reportable6 joined, statisfiable6 joined, benchable6 joined 01:03 evalable6 joined, linkable6 joined, coverable6 joined, bisectable6 joined, squashable6 joined 01:04 notable6 joined, unicodable6 joined, committable6 joined, bloatable6 joined, sourceable6 joined, releasable6 joined 01:05 nativecallable6 joined, tellable6 joined, shareable6 joined 02:05 linkable6 left, squashable6 left, notable6 left, benchable6 left, bloatable6 left, nativecallable6 left, unicodable6 left, greppable6 left, reportable6 left, evalable6 left, statisfiable6 left, tellable6 left, releasable6 left, coverable6 left, committable6 left, sourceable6 left, shareable6 left, quotable6 left, coverable6 joined, quotable6 joined 02:06 linkable6 joined, shareable6 joined, sourceable6 joined, committable6 joined, benchable6 joined, evalable6 joined, squashable6 joined, nativecallable6 joined, tellable6 joined, releasable6 joined 02:07 bloatable6 joined, unicodable6 joined, reportable6 joined, greppable6 joined, notable6 joined 02:08 statisfiable6 joined
MasterDuke [Coke]: i don't really know, i'm going off of what azure has, which is just windows server 2019 and 2022 02:23
ugexe MasterDuke: just a wild guess, but I wonder if the path to VS changed. Yours using 'Program Files (x86)' still, but when I look at when I updated my appveyor files I see I stopped using (x86) - github.com/ugexe/zef/commit/448863...5377649cf4 02:41
so maybe the detection here isn't working because vswhere.exe is in that different path - github.com/MoarVM/MoarVM/blob/0454...ml#L12-L13 02:42
MasterDuke thanks, i'll try messing around with that 02:43
ugexe MasterDuke: I just looked on a windows 11 VM with VS 2022 and vswhere is in that 86 location, so I guess thats not it 02:51
MasterDuke hm, that led me to some more googling which suggests vswhere + azure + windows 2022 are problematic and i don't think can easily be fixed by only changing paths
e.g., github.com/microsoft/vswhere/issues/250 02:52
 i think i'm going to back the windows change out of the pr, that can be handled later by someone who knows more about them than i do
ugexe i wonder what vswhere.exe is outputting on azure 02:54
04:03 linkable6 left, evalable6 left 04:04 evalable6 joined, linkable6 joined
Geth MoarVM/master: 8 commits pushed by (Daniel Green)++, MasterDuke17++ 05:01
06:00 reportable6 left 06:02 reportable6 joined 08:58 sena_kun joined 10:32 frost joined 12:00 reportable6 left, reportable6 joined 12:46 discord-raku-bot left, discord-raku-bot joined 13:46 evalable6 left 13:47 evalable6 joined 14:47 linkable6 left, evalable6 left, linkable6 joined 14:48 evalable6 joined
Geth MoarVM: 34bae78d45 | (Stefan Seifert)++ | 4 files
Work around "const_iX NYI" after getlexstatic_o with fallback resolver

getlexstatic_o and sp_getlexstatic_o did not take into account that MVM_frame_find_lexical_by_name may now dispatch if a fallback resolver is in use.
Note: this fix is _not_ complete as it completely ignores that we have ... (5 more lines)
17:45 Nicholas left 18:00 reportable6 left 18:01 reportable6 joined 18:25 Geth left, Geth joined 18:54 Nicholas joined 22:00 frost left 22:32 sena_kun left