Page MenuHomePhabricator

Provide a more structured result log for Herald conditions
ClosedPublic

Authored by epriestley on Feb 17 2021, 9:48 PM.
Tags
None
Referenced Files
F19930286: D21563.id51353.diff
Wed, Apr 8, 10:36 PM
F19916120: D21563.diff
Fri, Apr 3, 8:47 PM
F19813338: D21563.diff
Mar 4 2026, 8:42 AM
F19803198: D21563.id51334.diff
Mar 1 2026, 9:38 PM
F19801583: D21563.id51334.diff
Mar 1 2026, 2:16 AM
F19795096: D21563.id.diff
Feb 26 2026, 10:39 PM
F19689452: D21563.diff
Feb 9 2026, 9:08 PM
F19648308: D21563.id.diff
Feb 6 2026, 5:29 AM
Subscribers
None

Details

Summary

Ref T13586. Currently, Herald condition logs encode "pass" or "fail" robustly, "forbidden" through a sort of awkward side channel, and can not properly encode "invalid" or "exception" outcomes.

Structure the condition log so results are represented unambiguously and all possible outcomes (pass, fail, forbidden, invalid, exception) are clearly encoded.

Test Plan

Screen Shot 2021-02-17 at 1.30.55 PM.png (755×1 px, 173 KB)

Screen Shot 2021-02-17 at 1.35.55 PM.png (705×1 px, 142 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable