*: prepare for real-tikv-test on next gen

[D3Hunter]

What problem does this PR solve?

Issue Number: ref #60418

Problem Summary:

What changed and how does it work?

use the same NEXT_GEN=1 to control next gen real-tikv test

Check List

Tests

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

see the define gotags= part

➜  tidb git:(one-writer-ondup) ✗ make --dry-run bazel_importintotest3
GOBIN=/Users/jujiajia/code/pingcap/tidb/tools/bin GO111MODULE=on go install github.com/pingcap/failpoint/failpoint-ctl@9b3b6e3
find $PWD/ -mindepth 1 -type d | grep -vE "(\.git|\.idea|tools)" | xargs tools/bin/failpoint-ctl enable
bazel  run  //:gazelle
bazel  run   \
	--run_under="cd /Users/jujiajia/code/pingcap/tidb && " \
	 //tools/tazel:tazel
bazel  test  --test_output=all --test_arg=-with-real-tikv --define gotags=deadlock,intest \
	-- //tests/realtikvtest/importintotest3/...

➜  tidb git:(one-writer-ondup) ✗ NEXT_GEN=1 make --dry-run bazel_importintotest3
GOBIN=/Users/jujiajia/code/pingcap/tidb/tools/bin GO111MODULE=on go install github.com/pingcap/failpoint/failpoint-ctl@9b3b6e3
find $PWD/ -mindepth 1 -type d | grep -vE "(\.git|\.idea|tools)" | xargs tools/bin/failpoint-ctl enable
bazel  run  //:gazelle
bazel  run   \
	--run_under="cd /Users/jujiajia/code/pingcap/tidb && " \
	 //tools/tazel:tazel
bazel  test  --test_output=all --test_arg=-with-real-tikv --define gotags=deadlock,intest,nextgen \
	-- //tests/realtikvtest/importintotest3/...

• 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 @D3Hunter. 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.

Details

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 73.5435%. Comparing base (d5b1f58) to head (498d490).
Report is 3 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #60892        +/-   ##
================================================
+ Coverage   73.1364%   73.5435%   +0.4071%     
================================================
  Files          1722       1722                
  Lines        476542     476580        +38     
================================================
+ Hits         348526     350494      +1968     
+ Misses       106616     104692      -1924     
+ Partials      21400      21394         -6     

Flag	Coverage Δ
integration	42.5727% <ø> (?)
unit	72.3568% <ø> (ø)

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

Components	Coverage Δ
dumpling	52.7118% <ø> (ø)
parser	∅ <ø> (∅)
br	47.3515% <ø> (+0.0082%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Benjamin2037]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-04-28 08:04:26.340893705 +0000 UTC m=+861210.152684086: ☑️ agreed by hawkingrei.
• 2025-04-28 09:18:35.132756685 +0000 UTC m=+865658.944547065: ☑️ agreed by Benjamin2037.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Benjamin2037, hawkingrei, tangenta

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [Benjamin2037,hawkingrei,tangenta]

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