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.