Blue
Blue
Thank you @joelhellman. Out of curiosity, do you have a .wslconfig ? If so can you share its contents ?
> @OneBlue - looks like pipelines aren't getting triggered. Yeah I'm still working on it
> > There is another similar compiler warning with memset probably. > > ``` > > src/linux/init/init.cpp:1075:12: warning: first argument in call to 'memset' is a pointer to non-trivially copyable...
> Should we add a test where we install mono and make sure interop still works? I want to do that, but we've made it so the tests don't try...
The test failures are caused by a cloudtest change, merging since the test failures are unrelated.
Thank you for reporting this @thendricks0. WSL 2.6.2 indeed updated to wslg 1.0.71. Transferring to wslg for deeper investigation.
Thank you @epineda. From the logs it appears that WSL gets into a bad state. Let's see what's happening inside the VM. Can you please: - reproduce the issue -...
Thank you @fire332. Based on the logs you shared it looks like init might be blocked on a signal. Here's an updated script that should tell us which signal is...
Thank you @fire332. So from what I can see, a bunch of Linux processes seem to get into a weird state, with kernel stacks like these: ``` [] get_signal+0x8b6/0xa90 []...