-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
admission: fix overflow bug in ioLoadListener #69567
Conversation
Fixes cockroachdb#69461,cockroachdb#69463 Release justification: High-severity bug fix to new funtionality. Release note: None
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you say a few words here about how the bug triggered? Feels like when the code was originally written, we assumed that we would only hit the MaxInt64
endpoint and not MaxInt64 - small_number
. (I lack the understanding of what the context of this code is).
Also, I think this fixes all of these: https://github.com/cockroachdb/cockroach/issues?q=is%3Aopen+is%3Aissue+label%3AC-test-failure+assignee%3Asumeerbhola+
Reviewed 2 of 2 files at r1, all commit messages.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @RaduBerinde)
TFTR!
I still don't know. I've been trying to reproduce the roachtest failures with additional instrumentation, but haven't been successful so far. I'll keep trying this afternoon, since it might uncover some other badness. Meanwhile I'll merge this. |
bors r+ |
btw, do you know what exit code 134 is? I could not find it in
|
You need to look at |
Ah, 134 is just 128+SIGABRT |
I don't get it.. How would |
I'd add more assertions: check that |
So is it code 7 which is
I can't even get the current assertion to fire, at least based on looking at the logs. And the extra logging I added shows sane values. |
Build succeeded: |
I'm not sure where the exit code comes from. On a panic like the one hit in these tests, the exit code should be 2. We invoke CRDB through systemd via a shell script, this may make a difference, but the exit code grabbed from the crdb process within that script is also 134 as evidenced by the log files. cockroach/pkg/cmd/roachprod/install/scripts/start.sh Lines 57 to 61 in 0de4773
|
I have a reproduction -- this PR is not going to fix it since |
Is it because |
It was simpler than that -- |
Fixes #69461,#69463
Release justification: High-severity bug fix to new funtionality.
Release note: None