sagudev
sagudev
One thing that could be relevant for us is policy by mozilla (given that we share some code and send patches there), but when I asked about it I got...
> > One thing that could be relevant for us is policy by mozilla > > Here is the Mozilla policy for community contributors in general: https://support.mozilla.org/en-US/kb/contributor-policy-generative-ai-usage I was searching...
> Ah, this explains the recent issue I had on windows. I should probably add workaround in mach instead of CI file. > Do we need to use crown on...
> Is there anything blocking this? Not anything that I know of. CC @jdm @mrobinson
> I'm ok with that. We may want to start by updating thevPR template to have a checklist item about running crown if any script changes are included. CI would...
Current try run: https://github.com/sagudev/servo/actions/runs/9205601757/job/25323173909
I think I will not deal with `_webgpu/webgpu/cts.https.html?q=webgpu:api,operation,adapter,requestDevice:invalid:*` in this PR as wgpu-core allows creating multiple valid devices from same adapter, but spec doesn't.
new run: https://github.com/sagudev/servo/actions/runs/9211814858/job/25343380939 `_webgpu/webgpu/cts.https.html?q=webgpu:api,validation,state,device_lost,destroy` has (only in CI): ``` PASS [expected TIMEOUT] subtest: :stage="finish";awaitLost=true PASS [expected NOTRUN] subtest: :stage="finish";awaitLost=false PASS [expected NOTRUN] subtest: :stage="submit";awaitLost=true FAIL [expected NOTRUN] subtest: :stage="submit";awaitLost=false assert_unreached:...
`endTestScope timed out` are happening because WGPU thread is stuck in deadlock: https://github.com/gfx-rs/wgpu/issues/5737