You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a wgpu issue that we need to work around: gfx-rs/wgpu#1010 I started experimenting with a patch that makes texture creation fallible by checking device limits and changing some APIs to return Result.
I ran into a number of problems with automated testing. The big one is that pixels-mocks is still not runnable (but it's ok for compilation tests). See #80. Using winit in integration tests has some issues with creating the event-loop off the main thread, at least on Windows. It can be done with platform-specific extensions. And then tests may not be able to run on all platforms.
The text was updated successfully, but these errors were encountered:
There is a
wgpu
issue that we need to work around: gfx-rs/wgpu#1010 I started experimenting with a patch that makes texture creation fallible by checking device limits and changing some APIs to returnResult
.I ran into a number of problems with automated testing. The big one is that
pixels-mocks
is still not runnable (but it's ok for compilation tests). See #80. Usingwinit
in integration tests has some issues with creating the event-loop off the main thread, at least on Windows. It can be done with platform-specific extensions. And then tests may not be able to run on all platforms.The text was updated successfully, but these errors were encountered: