Started by GitHub push by ti-chi-bot[bot]Started by GitHub push by ti-chi-bot[bot]0027070270701270121270121.006528652812522196747ee59d0a69adab1fd3e6a2331afaf6ddaa2196747ee59d0a69adab1fd3e6a2331afaf6ddaaorigin/main2196747ee59d0a69adab1fd3e6a2331afaf6ddaa2196747ee59d0a69adab1fd3e6a2331afaf6ddaaorigin/main2196747ee59d0a69adab1fd3e6a2331afaf6ddaa2196747ee59d0a69adab1fd3e6a2331afaf6ddaaorigin/mainhttps://github.com/PingCAP-QE/ci.gitfalse#125212701283303seed #12521252falsefalse12522742576SUCCESS1766044107884https://do.pingcap.net/jenkins/view/all/job/seed/1252/default-pn8drtools/reporters/ci/flaky-tests/core/OwnerResolver.test.tstools/reporters/ci/flaky-tests/core/OwnerResolver.tstools/reporters/ci/flaky-tests/core/types.ts2196747ee59d0a69adab1fd3e6a2331afaf6ddaa1766044069000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comfix: prioritize exact suite matches over parent suite matches (#4008) ### Summary I successfully fixed the issue where the flaky owner for the `pkg/executor/importer` package was incorrectly reported as `sunruoxi@pingcap.com` instead of `bear.c@pingcap.com`. ### Root Cause The problem was in the `OwnerResolver.resolveViaMap` method in `/tools/reporters/ci/flaky-tests/core/OwnerResolver.ts`. The logic didn't properly distinguish between exact suite matches and parent suite prefix matches when assigning the resolution level. Both types of matches were assigned the same level ("suite"), causing the first encountered match to win when priorities were equal. ### Changes Made 1. **Updated `types.ts`**: Added a new `OwnerResolutionLevel` value `"parent-suite"` to distinguish between exact suite matches and parent suite prefix matches. 2. **Updated `OwnerResolver.ts`**: - Modified the level assignment logic to use `"suite"` for exact matches and `"parent-suite"` for prefix matches - Updated the level ranking to give exact suite matches (level 3) higher precedence than parent suite matches (level 2) 3. **Updated `OwnerResolver.test.ts`**: - Fixed the import statement for `assertEquals` - Updated the test case type to include the new `"parent-suite"` level - Updated the existing parent suite test case to expect `"parent-suite"` level instead of `"suite"` - Added a new test case specifically for the exact vs parent suite precedence issue 2025-12-18 07:47:49 +00002196747ee59d0a69adab1fd3e6a2331afaf6ddaafix: prioritize exact suite matches over parent suite matches (#4008)edittools/reporters/ci/flaky-tests/core/types.tsedittools/reporters/ci/flaky-tests/core/OwnerResolver.test.tsedittools/reporters/ci/flaky-tests/core/OwnerResolver.tsgithttps://do.pingcap.net/jenkins/user/noreplynoreply