[cascade] Reset generation bits
There was a bug in CascadePriority, when creating priorities with a 'generation'. This constructor was supposed to _set_ the generation, not bitwise-or with the previous generation. Bug: 947004 Change-Id: Ie3471f6a3052c0f3ca8454151a8f46839558d5a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2106064Reviewed-by:Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#750949}
Showing
Please register or sign in to comment