pingcap/tidb

some explain test case should ignore plan-id in the result file

Open

#60,940 建立於 2025年4月29日

在 GitHub 查看
 (4 留言) (0 反應) (1 負責人)Go (40,090 star) (6,186 fork)batch import
good first issuesig/plannertype/enhancement

描述

Enhancement

Some explain-test cases will record the plan ID in the result file, which will be a burden when some optimization flow is changed, since plan ID allocation is sequential according to the allocation order or space.

貢獻者指南

技術棧
gosql
領域
databasetesting
議題類型
test
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Go programmingTiDB test framework
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
Look at the explain test cases in the TiDB repository, likely in the `tests/integration tests` or similar directories. The plan id appears in expected output files. The goal is to ignore the specific plan id field in comparisons, possibly by using a placeholder or by modifying the test framework to skip that field. Check existing test patterns that handle non deterministic output. The fix likely involves updating the test case files or the test runner to strip out plan id values before comparison.
some explain test case should ignore plan-id in the result file · pingcap/tidb#60940 | Good First Issue