-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Making WebGPU-NAPI addon @webgpu compliant #5
Comments
The CTS testing for WebGPU-NAPI is proceeding with Kai at Google. Getting an error here, looking into it now. Any suggestions? FATAL ERROR: Error::New napi_get_last_error_info
|
@dcerisano so you were able to reproduce that issue locally? What did you change to make that issue start happening? |
I had the LD_LIBRARY path set to the latest build of Dawn. The binaries in the PR are from July 10. We need to roll upstream Dawn changes into WebGPU-NAPI on a regular basis. I included a build.sh in our fork that builds the July 10 version of Dawn (will make it a submodule eventually). Dawn does not have tags, so referencing by commit SHA for July 10. |
I just posted an update to your issue in CTS
Could you please create a cts-napi branch here to develop against the napi branch in CTS?
The basic issue is that there are slight differences in WebGPU API between these two repos that should be resolved. The idea to to make everything compliant with the @webgpu spec.
This will likely mean the addition of typescript to the examples here, to ensure the NAPI addon remains compliant and is instantly aware of changes to the @webgpu spec.
The text was updated successfully, but these errors were encountered: