ddl: make test TestRenameTableAutoIDs more stable

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #53765

Problem Summary:

What changed and how does it work?

The root cause is the same with this one #54447
When we do ddl, wait ddl status change to finish is not enough.
We need to wait the infoschema reload finish, otherwise we may see the stale infoschema.

Here the test code execute renamte table renametableautoids.t to renametableautoids2.t2
Using the stale infoschema would get error :

        	Error:      	Received unexpected error:
        	            	[schema:1146]Table 'renametableautoids2.t2' doesn't exist
        	            	github.com/pingcap/errors.AddStack
        	            		external/com_github_pingcap_errors/errors.go:178

NOTE, rename table cross different DBs have known capatibility issue with autoid.
And even after this fix, the test may still be unstable by that capability issue.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @tiancaiamao. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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-sigs/prow repository.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.8626%. Comparing base (c4fd1b2) to head (e76b08b).
Report is 3 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #54695         +/-   ##
=================================================
- Coverage   72.7411%   55.8626%   -16.8786%     
=================================================
  Files          1551       1672        +121     
  Lines        437183     609368     +172185     
=================================================
+ Hits         318012     340409      +22397     
- Misses        99532     245721     +146189     
- Partials      19639      23238       +3599     

Flag	Coverage Δ
integration	36.9138% <ø> (?)
unit	71.7094% <ø> (-0.0451%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.9656% <ø> (ø)
parser	∅ <ø> (∅)
br	52.5834% <ø> (+6.7430%)	⬆️

[tiancaiamao]

/retest

[tiprow]

@tiancaiamao: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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-sigs/prow repository.

[mjonss]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-07-18 03:20:35.92789411 +0000 UTC m=+496857.918835565: ☑️ agreed by xhebox.
• 2024-07-18 04:41:30.601622077 +0000 UTC m=+501712.592563547: ☑️ agreed by mjonss.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mjonss, tangenta, xhebox

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:

• pkg/ddl/OWNERS [tangenta]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment