lightning: fix unstable test for conflict detection

[lyzx2001]

What problem does this PR solve?

Issue Number: ref #52306

Problem Summary:

What changed and how does it work?

Fix unstable test for lightning_duplicate_resolution_merge.
https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Ftidb%2Fpull_lightning_integration_test/detail/pull_lightning_integration_test/691/pipeline/

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 @lyzx2001. 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.

[lyzx2001]

/test pull-lightning-integration-test

[tiprow]

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

In response to this:

/test pull-lightning-integration-test

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.6600%. Comparing base (fa94f49) to head (b5244ac).
Report is 12 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #53225        +/-   ##
================================================
+ Coverage   72.4109%   74.6600%   +2.2490%     
================================================
  Files          1493       1515        +22     
  Lines        429341     439488     +10147     
================================================
+ Hits         310890     328122     +17232     
+ Misses        99162      90804      -8358     
- Partials      19289      20562      +1273     

Flag	Coverage Δ
integration	50.6896% <ø> (?)
unit	71.2539% <ø> (-0.0490%)	⬇️

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

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

[lyzx2001]

/cc @lance6716

[lance6716]

please find the root cause rather than remove the test. There should be 10 records of PK 1,2,3,4,5,6,13,14,15,16.

[lyzx2001]

/test pull-lightning-integration-test

[tiprow]

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

In response to this:

/test pull-lightning-integration-test

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.

[lyzx2001]

please find the root cause rather than remove the test. There should be 10 records of PK 1,2,3,4,5,6,13,14,15,16.

In log we can see that lightning 2 exited at 16:21:41.696, but lightning 1 met error "Table "lightning_metadata.task_meta_v2' doesn't exist" at 16:21:41.702, where we may infer lightning 2 deleted the table too soon. So the solution can be manually adding sleep time to extend the import time.

[lyzx2001]

/cc @D3Hunter

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, lance6716

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:

• lightning/OWNERS [D3Hunter,lance6716]

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-13 13:25:10.683945482 +0000 UTC m=+1486864.441081056: ☑️ agreed by lance6716.
• 2024-05-14 08:11:52.940787383 +0000 UTC m=+1554466.697922956: ☑️ agreed by D3Hunter.