chore: sqllogic test pod use specify node

[purelind]

User description

sqllogic test pod use specify node to avoid the test script from getting stuck

---

PR Type

enhancement

---

Description

• Added a node selector for ci-nvme-high-performance with value true in the latest pipeline configuration.
• Added a node selector for ci-nvme-high-performance with value true in the release-8.2 pipeline configuration.

---

Changes walkthrough 📝

Relevant files

Enhancement

pod-pull_sqllogic_test.yaml Add node selector for high-performance NVMe in latest pipeline pipelines/pingcap/tidb/latest/pod-pull_sqllogic_test.yaml Added a node selector for ci-nvme-high-performance with value true. +4/-0      pod-pull_sqllogic_test.yaml Add node selector for high-performance NVMe in release-8.2 pipeline pipelines/pingcap/tidb/release-8.2/pod-pull_sqllogic_test.yaml Added a node selector for ci-nvme-high-performance with value true. +5/-0

---

💡 PR-Agent usage: Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[ti-chi-bot[bot]]

I have already done a preliminary review for you, and I hope to help you do a better job.

Based on the PR title and description, it seems that the changes are related to specifying a node for the sqllogic test pod to avoid the test script from getting stuck. Looking at the diff, it appears that the change adds the ci-nvme-high-performance key to the pod spec with the value of true in both the latest and release-8.2 branches.

There are no potential problems that I can identify from this change. However, it would be helpful if the author could provide more context on why this change was necessary and how it solves the problem.

As for fixing suggestions, since this is a small change and there are no potential issues, it looks good to merge as is. However, it's always a good practice to have a peer review the code changes before merging.

[ti-chi-bot[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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: - **[pipelines/OWNERS](https://github.com/PingCAP-QE/ci/blob/main/pipelines/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[codiumai-pr-agent-pro[bot]]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

PR Reviewer Guide 🔍

⏱️ Estimated effort to review [1-5]	2
🧪 Relevant tests	No
🔒 Security concerns	No
⚡ Key issues to review	None

[codiumai-pr-agent-pro[bot]]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

PR Code Suggestions ✨

Category	Suggestion	Score
Maintainability	Improve the clarity of the value for 'ci-nvme-high-performance' ___ **Consider using a more descriptive value than "true" for the 'ci-nvme-high-performance' key to enhance clarity and maintainability. If the intention is to specify that the node should have NVMe with high performance, a more explicit value could better communicate the requirement.** [pipelines/pingcap/tidb/latest/pod-pull_sqllogic_test.yaml [33-36]](https://github.com/PingCAP-QE/ci/pull/3017/files#diff-18868a47ddbab92e0dca0746ff1f8901ba2e7e00ce1c7e19acf2e239b68e01d1R33-R36) ```diff - key: ci-nvme-high-performance operator: In values: - - "true" + - "enabled" ``` - [ ] **Apply this suggestion** Suggestion importance[1-10]: 7 Why: The suggestion to use a more descriptive value than "true" for the 'ci-nvme-high-performance' key enhances clarity and maintainability. However, it is a minor improvement and does not address any major bugs or issues.	7