pingcap / tipocket

A toolkit for testing TiDB
https://github.com/pingcap/tipocket
Apache License 2.0
140 stars 71 forks source link

do not fail if resolve lock returns region unavailable #432

Closed vivid392845427 closed 3 years ago

vivid392845427 commented 3 years ago

What problem does this PR solve?

the testcase return error message as follow,because nemesis:pd-scheduler random-merge-scheduler

2021/09/07 05:23:35 pd_scheduler.go:59: [info] apply nemesis pd-scheduler random-merge-scheduler on ns tipocket-debug-nrrdr 2021/09/07 05:23:35 pd_scheduler.go:63: [info] add scheduler random-merge-scheduler successfully 2021/09/07 05:27:34 resolve_lock.go:233: [error] [round-35] failed to run GC at safe point 427552777833021443 2021/09/07 05:27:34 resolve_lock.go:194: [info] test end 2021/09/07 05:27:34 control.go:285: [fatal] run client error, GET request "http://debug-tidb.tipocket-debug-nrrdr.svc:10080/test/gc/resolvelock?safepoint=427552777833021443&physical=false", got 400 resolveLocks failed: region unavailable

What is changed and how does it work?

none

Check List

Tests

Code changes

Side effects

Related changes

Does this PR introduce a user-facing change?:

NONE