tablecodec: igrate test-infra to testify

[jiaxiang521]

What problem does this PR solve?

Issue Number: close #26867

What is changed and how it works?

tablecodec:migrate test-infra to testify#26867.

Release note

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• mmyj
• xhebox

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[CLAassistant]

All committers have signed the CLA.

[ti-chi-bot]

Welcome @jiaxiang521!

It looks like this is your first PR to pingcap/tidb 🎉.

I'm the bot to help you request reviewers, add labels and more, See available commands.

We want to make sure your contribution gets all the attention it needs!



Thank you, and welcome to pingcap/tidb. 😃

[sre-bot]

Please follow PR Title Format:

• pkg [, pkg2, pkg3]: what is changed

Or if the count of mainly changed packages are more than 3, use

• *: what is changed

After you have format title, you can leave a comment /run-check_title to recheck it

[sre-bot]

Please follow PR Title Format:

• pkg [, pkg2, pkg3]: what is changed

Or if the count of mainly changed packages are more than 3, use

• *: what is changed

After you have format title, you can leave a comment /run-check_title to recheck it

[jiaxiang521]

/cc @tisonkun

[sre-bot]

Please follow PR Title Format:

• pkg [, pkg2, pkg3]: what is changed

Or if the count of mainly changed packages are more than 3, use

• *: what is changed

After you have format title, you can leave a comment /run-check_title to recheck it

[jiaxiang521]

/run-check_title

[sre-bot]

Please follow PR Title Format:

• pkg [, pkg2, pkg3]: what is changed

Or if the count of mainly changed packages are more than 3, use

• *: what is changed

After you have format title, you can leave a comment /run-check_title to recheck it

[jiaxiang521]

/run-check_title

[sre-bot]

Please follow PR Title Format:

• pkg [, pkg2, pkg3]: what is changed

Or if the count of mainly changed packages are more than 3, use

• *: what is changed

After you have format title, you can leave a comment /run-check_title to recheck it

[tisonkun]

@jiaxiang521 there should be a blank between : and the next chapter :(

[tisonkun]

/run-check_title

[tisonkun]

Almost LGTM.

[ti-chi-bot]

@tisonkun: Thanks for your review. The bot only counts approvals from reviewers and higher roles in list, but you're still welcome to leave your comments.

In response to this:

Almost LGTM.

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.

[tisonkun]

/cc @xhebox @mmyj

[ti-chi-bot]

@tisonkun: GitHub didn't allow me to request PR reviews from the following users: mmyj.

Note that only pingcap members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @xhebox @mmyj

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 kubernetes/test-infra repository.

[tisonkun]

Be aware the next time that "```release-note" the "release-note" part is significant.

[jiaxiang521]

Be aware the next time that "```release-note" the "release-note" part is significant.

ok, I will

[mmyj]

lgtm

[xhebox]

/cc @mmyj plz help merging

[ti-chi-bot]

@xhebox: GitHub didn't allow me to request PR reviews from the following users: mmyj, plz, merging.

Note that only pingcap members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @mmyj plz help merging

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 kubernetes/test-infra repository.

[mmyj]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 864226bf1c2b63465dd3f3acccbb4f9e565ffebb

[mmyj]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
3 out of 4 committers have signed the CLA.

✅ tisonkun
✅ ti-chi-bot
✅ jiaxiang521
❌ water521

water521 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@tisonkun @jiaxiang521 We need to resolve it?

[tisonkun]

@jiaxiang521 could you please squash commit into one manually? I think it is because you commit with a local user that doesn't sign off CLA and trigger the blocker.

[tisonkun]

or just edit this commit with new author as yourself 328a4dc

[tisonkun]

Well. Let me do it for you...

[tisonkun]

@mmyj I fix the CLA problem. You can check whether the diff is the same as before rebase, and if so, trigger merge again.

[mmyj]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 77bbf82

[jiaxiang521]

@jiaxiang521 could you please squash commit into one manually? I think it is because you commit with a local user that doesn't sign off CLA and trigger the blocker.
Sorry, I think it is because i commit with another computer at weekends.

[tisonkun]

@jiaxiang521 never mind. It is done :)