fix(upscaling): fix motion vectors underwater#2023
Conversation
…haders that broke frame gen
📝 WalkthroughWalkthroughA removal of the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
No actionable suggestions for changed features. |
|
fixes issue #1766 |
|
@claude what is wrong with the tests |
|
@coderabbitai what is wrong with the tests |
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain🏁 Script executed: Length of output: 6637 🏁 Script executed: Length of output: 50343 🏁 Script executed: Length of output: 10590
The failure is deep inside A few things that confirm this is a CI infrastructure issue:
This is likely a transient runner issue (e.g., resource pressure or an MSVC regression on the CI machine). You can try re-running the failed jobs from the Actions page to see if they pass on a fresh runner. 🧠 Learnings used |
|
Wait. This may fix a single bad path, but this will impact any define where the motion vectors aren't defined. We need to confirm this pattern doesn't happen more. |
|
Unrelated CI failure, #2026 |
closes community-shaders#2021 (cherry picked from commit 15df3df)
Summary by CodeRabbit