*: fix unstable assert for location

[lcwangchao]

What problem does this PR solve?

Issue Number: close #53375

Problem Summary:

Some tests are unstable for assertations of location:

[2024/05/17 07:32:17.193 +00:00] [INFO] [job_table.go:349] ["the owner sets owner operator value"] [category=ddl] [ownerOp=none]

panic: assert failed, location mismatch, ctxLoc: UTC, varsLoc: UTC, stmtLoc: UTC [recovered]

	panic: assert failed, location mismatch, ctxLoc: UTC, varsLoc: UTC, stmtLoc: UTC

The assert fails because the underlayer pointers of location are the not the same. However this assert should pass because they are the same location in fact

What changed and how does it work?

Compare location name instead of pointer

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 @lcwangchao. 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 74.6016%. Comparing base (f5ac93e) to head (92b0301).
Report is 18 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #53376        +/-   ##
================================================
+ Coverage   72.6008%   74.6016%   +2.0007%     
================================================
  Files          1505       1505                
  Lines        429827     431524      +1697     
================================================
+ Hits         312058     321924      +9866     
+ Misses        98576      89692      -8884     
- Partials      19193      19908       +715     

Flag	Coverage Δ
integration	49.3308% <100.0000%> (?)
unit	71.3186% <100.0000%> (-1.2741%)	⬇️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	50.3450% <ø> (+8.9444%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tangenta, XuHuaiyu

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/expression/OWNERS [XuHuaiyu]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-05-20 03:02:51.430143253 +0000 UTC m=+2054325.187278819: ☑️ agreed by tangenta.
• 2024-05-22 03:07:51.961764356 +0000 UTC m=+2227425.718899930: ☑️ agreed by XuHuaiyu.

[lcwangchao]

/retest

[tiprow]

@lcwangchao: 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.