Deep verify falls through to manual UAT when unavailable #165
Labels
No labels
already-shipped
bug
documentation
duplicate
enhancement
external-review
good first issue
help wanted
in progress
invalid
needs-decision
proposal
question
security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: crenshawdev/cadence-archived#165
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Source: strict re-review C-24
Verdict: DISPUTE - by design, closing
Claim as reviewed
Deep verify is designed to fall through to manual UAT if unavailable, so automated verification availability is not a completion invariant.
At HEAD
f354864(v3.3.0)Accurate, and the review itself calls this "good fail-visible behavior".
Note
Falling through to a human with the reason named is the correct degradation for a verifier that could not run. The alternative - blocking a phase because a reviewer was unreachable - trades a visible manual step for a hard stop.
Not a defect.