sorter: fix the bug that value can be corrupted when accessing sorter #11548
Conversation
ti-chi-bot
bot
added
do-not-merge/cherry-pick-not-approved
release-note-none
Signed-off-by: qupeng <[email protected]>
hicqu
force-pushed
the
6.5-fix-pebble-fetch
branch
from
fd2f4d8
to
4f5afa4
Compare
ti-chi-bot
bot
added
size/S
[LGTM Timeline notifier]Timeline:
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 3AceShowHand, asddongmen, lidezhu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ti-chi-bot
bot
added
cherry-pick-approved
|
/cherry-pick release-6.5-fips |
|
@hicqu: cannot checkout In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
|
/cherry-pick feature/release-6.5-fips |
|
@hicqu: new pull request created to branch In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
#11548) #11557 Signed-off-by: qupeng <[email protected]> Co-authored-by: qupeng <[email protected]>
|
/cherry-pick release-7.1 |
|
@hicqu: new pull request created to branch In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
What problem does this PR solve?
Issue Number: close #6367
Issue Number: close #10853
What is changed and how it works?
This PR is extracted from #10899 , which fixes the bug that value can be corrupted when accessing sorter.
It's hard to construct a test case for the change because the value corruption can't be reproduced stable. So we just ignore it.
Check List
Tests
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note