tide does not correctly perceive the context of failure

[purelind]

Bug Report

• I have searched the issues of this repository and believe that this is not a duplicate.

Related link

• Which project: pingcap/docs and pingcap/docs-cn

• PR or Issue Link: vaunt: update achievement images and add vaunt documentation pingcap/docs-cn#16466

Steps to reproduce(Optional)

In the case where PR already has approved and LGTM labels, if the pull-verify pipeline fails, Tide may display "in merge pool". This situation is unexpected when the pull-verify context fails.

What is expected?

At this time, tide should prompt that the pull-verify execution has failed and should not enter the merge queue.

What is actually happening?

[ti-chi-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-community-infra or wuhuizuo.
/lifecycle stale

[ti-chi-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-community-infra or Mini256.
/lifecycle rotten