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
Unknown Object (File)
Sun, Dec 1, 12:40 PM
Unknown Object (File)
Sun, Dec 1, 12:40 PM
Unknown Object (File)
Sun, Dec 1, 8:02 AM
Unknown Object (File)
Nov 16 2024, 10:38 PM
Unknown Object (File)
Oct 9 2024, 1:50 PM
Unknown Object (File)
Oct 1 2024, 4:58 AM
Unknown Object (File)
Sep 26 2024, 11:44 AM
Unknown Object (File)
Sep 24 2024, 4:58 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