-
Notifications
You must be signed in to change notification settings - Fork 908
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
Automated tests fail on Mac OS 10.13 #4632
Comments
There are two issues here:
|
For comparison here's the same test run on trunk (last commit Nov 04) |
Looking at the logs we get the following errors:
|
Seems to be: from https://developer.apple.com/metal/Metal-Shading-Language-Specification.pdf But it's unclear if this limitation has been lifted in some of the newer Metal versions since we haven't gotten any other reports of this. https://developer.apple.com/forums/thread/665272 is asking the same thing. |
Upgraded to 1d4fa81 to get PR #4643 and reran tests |
Last time I checked (early Summer) wgpu was informally supported on MacOS back to 10.13. This made me happy as I am trying to maintain one machine on 10.13. I asked today in the wgpu Matrix what would have to happen for wgpu to formally ("documented in README") support MacOS back to 10.13. cwfitzgerald said at minimum we would need to successfully run
cargo xtask test
on 10.13. I volunteered to try this.I installed nextest, checked out the 0.18.0 tag and ran the test command. Nearly all tests failed, including basic tests like test_api. This was a surprise to me, to the extent I suspect something is wrong with the test runner, because on the same machine (MacBookPro12,1 with integrated Intel Iris Graphics 6100, macOS 10.13.6 17G14042) I can successfully run any wgpu examples I like (for example, hello-triangle).
Expected behavior: Unless you have made a conscious decision to stop supporting 10.13, the tests should work on 10.13
0.18.TEST.TXT
The text was updated successfully, but these errors were encountered: