Skip to content

test: skip some upgrade tests for next-gen#63331

Merged
ti-chi-bot[bot] merged 3 commits into
pingcap:masterfrom
CbcWestwolf:skip_next_gen_bootstrap_test
Sep 2, 2025
Merged

test: skip some upgrade tests for next-gen#63331
ti-chi-bot[bot] merged 3 commits into
pingcap:masterfrom
CbcWestwolf:skip_next_gen_bootstrap_test

Conversation

@CbcWestwolf

Copy link
Copy Markdown
Member

What problem does this PR solve?

Issue Number: ref #61702

Problem Summary:

Since in next-gen cluster all tables that are created by bootstrap can not have non-clustered primary key, we can skip the test cases containing upgradeToVer248

What changed and how does it work?

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

@ti-chi-bot ti-chi-bot Bot added release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Sep 2, 2025
@CbcWestwolf

Copy link
Copy Markdown
Member Author

/test pull-unit-test-next-gen

@tiprow

tiprow Bot commented Sep 2, 2025

Copy link
Copy Markdown

@CbcWestwolf: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test fast_test_tiprow
  • /test tidb_parser_test

Use /test all to run all jobs.

Details

In response to this:

/test pull-unit-test-next-gen

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 Bot commented Sep 2, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.2624%. Comparing base (3d9a0eb) to head (6dafc78).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files
@@               Coverage Diff                @@
##             master     #63331        +/-   ##
================================================
+ Coverage   72.7832%   73.2624%   +0.4791%     
================================================
  Files          1832       1832                
  Lines        495794     496159       +365     
================================================
+ Hits         360855     363498      +2643     
+ Misses       113010     110814      -2196     
+ Partials      21929      21847        -82     
Flag Coverage Δ
integration 42.0544% <ø> (?)
unit 72.3309% <ø> (+0.0788%) ⬆️

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

Components Coverage Δ
dumpling 52.8700% <ø> (ø)
parser ∅ <ø> (∅)
br 46.5345% <ø> (+0.0025%) ⬆️
🚀 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.

@CbcWestwolf

Copy link
Copy Markdown
Member Author

/test pull-unit-test-next-gen

@tiprow

tiprow Bot commented Sep 2, 2025

Copy link
Copy Markdown

@CbcWestwolf: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test fast_test_tiprow
  • /test tidb_parser_test

Use /test all to run all jobs.

Details

In response to this:

/test pull-unit-test-next-gen

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.

@CbcWestwolf

Copy link
Copy Markdown
Member Author

/test pull-unit-test-next-gen

@tiprow

tiprow Bot commented Sep 2, 2025

Copy link
Copy Markdown

@CbcWestwolf: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test fast_test_tiprow
  • /test tidb_parser_test

Use /test all to run all jobs.

Details

In response to this:

/test pull-unit-test-next-gen

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.

@CbcWestwolf

Copy link
Copy Markdown
Member Author

/test pull-unit-test-next-gen

@tiprow

tiprow Bot commented Sep 2, 2025

Copy link
Copy Markdown

@CbcWestwolf: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test fast_test_tiprow
  • /test tidb_parser_test

Use /test all to run all jobs.

Details

In response to this:

/test pull-unit-test-next-gen

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.

@CbcWestwolf

Copy link
Copy Markdown
Member Author

/retest

1 similar comment
@CbcWestwolf

Copy link
Copy Markdown
Member Author

/retest

@ti-chi-bot

ti-chi-bot Bot commented Sep 2, 2025

Copy link
Copy Markdown

@CbcWestwolf: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
non-block/pull-unit-test-next-gen 798955d link false /test pull-unit-test-next-gen

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@ti-chi-bot ti-chi-bot Bot added approved needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Sep 2, 2025
@D3Hunter D3Hunter changed the title test: skip some upgration tests for next-gen test: skip some upgrade tests for next-gen Sep 2, 2025
Comment thread pkg/server/handler/tests/http_handler_test.go Outdated
Co-authored-by: D3Hunter <jujj603@gmail.com>
}

func TestIssue17979_1(t *testing.T) {
if kerneltype.IsNextGen() {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this related to upgrade?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, they call BootstrapSession

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

normal bootstrap also call BootstrapSession, i mean does it call the upgrade process?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the call stack is
image

}

func TestIssue17979_2(t *testing.T) {
if kerneltype.IsNextGen() {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this too

@ti-chi-bot

ti-chi-bot Bot commented Sep 2, 2025

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, 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:

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 ti-chi-bot Bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Sep 2, 2025
@ti-chi-bot

ti-chi-bot Bot commented Sep 2, 2025

Copy link
Copy Markdown

[LGTM Timeline notifier]

Timeline:

  • 2025-09-02 09:58:08.773036761 +0000 UTC m=+866180.650867715: ☑️ agreed by tangenta.
  • 2025-09-02 14:00:36.774296217 +0000 UTC m=+880728.652127171: ☑️ agreed by D3Hunter.

@ti-chi-bot ti-chi-bot Bot merged commit bb8af19 into pingcap:master Sep 2, 2025
26 checks passed
@CbcWestwolf CbcWestwolf deleted the skip_next_gen_bootstrap_test branch September 2, 2025 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved lgtm release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants