-
Notifications
You must be signed in to change notification settings - Fork 4k
allocator: correct logging for priority assertion #152675
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
Conversation
This commit fixes an incorrect log statement in computeAction for priority assertions. The log was mistakenly emitted even when the priority was not -1. Related: cockroachdb#152512 Release note: none
|
It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR? 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
|
TFTR! bors r=tbg |
152675: allocator: correct logging for priority assertion r=tbg a=wenyihu6 This commit fixes an incorrect log statement in computeAction for priority assertions. The log was mistakenly emitted even when the priority was not -1. Related: #152512 Epic: none Release note: none Co-authored-by: wenyihu6 <wenyi@cockroachlabs.com>
|
Build failed: |
|
CI seems to be hanging https://mesolite.cluster.engflow.com/invocations/default/6a2e3406-7dca-49e2-af9b-c03aa265990d. Not sure why. bors retry |
|
It's a pre-emption of the VM running the CI job. |
This commit fixes an incorrect log statement in computeAction for priority
assertions. The log was mistakenly emitted even when the priority was not -1.
Related: #152512
Epic: none
Release note: none