Updated to nightly-2022-04-18

[oisyn]

This also fixes #907.

[eddyb]

I think you just need to run cargo compiletest --bless to get the updated diagnostics output.

[eddyb]

What's going on here, do we automatically use the latest external spirv-tools on macOS?
I might need to play around with CI on main to get a better idea of what we're dealing with.

EDIT: started: https://github.com/EmbarkStudios/rust-gpu/runs/7880218068?check_suite_focus=true
(original was: https://github.com/EmbarkStudios/rust-gpu/runs/7826423572?check_suite_focus=true)

EDIT2: oh yeah you can see the bew-installed version going from 2022.2 to 2022.3.

[Jake-Shadle]

Yes, if not compiling from source the spirv binaries in PATH are used, so any time the github runners change those binaries there is a risk of breakage.

[eddyb]

Yes, if not compiling from source the spirv binaries in PATH are used, so any time the github runners change those binaries there is a risk of breakage.

Can't we just pass a version to brew install? These don't even come with GHA, we appear to install them ourselves in CI explicitly.

[Jake-Shadle]

In that case I guess you could specify the exact version, however one does that with brew.

[eddyb]

In that case I guess you could specify the exact version, however one does that with brew.

Turns out that one does not do that with brew, and after having my optimism crushed I ended up with:

• Use the same official SPIRV-Tools builds for macOS CI too. #910

(which involved digging through the spirv-tools Google Cloud Storage bucket for the right URL...)