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
F19083433: D21563.id51353.diff
Dec 2 2025, 12:35 PM
F19003231: D21563.id51353.diff
Nov 21 2025, 8:09 AM
F18993610: D21563.id51334.diff
Nov 19 2025, 8:12 AM
F18969567: D21563.diff
Nov 15 2025, 6:45 AM
F18826245: D21563.id51353.diff
Oct 24 2025, 3:09 AM
F18803659: D21563.id.diff
Oct 18 2025, 2:27 AM
F18798970: D21563.diff
Oct 17 2025, 10:20 AM
F18734399: D21563.id.diff
Sep 30 2025, 10:53 PM
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