Page MenuHomePhabricator

Make it easier to diagnose command failures inside Drydock
AbandonedPublic

Authored by hach-que on Nov 18 2015, 2:48 PM.
Tags
None
Referenced Files
F18803399: D14507.id35095.diff
Oct 17 2025, 11:23 PM
F18785780: D14507.id.diff
Oct 14 2025, 11:50 AM
F18757162: D14507.id.diff
Oct 5 2025, 3:48 PM
F18746592: D14507.diff
Oct 3 2025, 12:53 PM
F18467586: D14507.diff
Sep 2 2025, 1:06 PM
F18073241: D14507.id.diff
Aug 4 2025, 5:15 PM
F18053437: D14507.id35095.diff
Aug 4 2025, 5:02 AM
F18007801: D14507.diff
Aug 2 2025, 2:24 PM
Tokens
"Like" token, awarded by joshuaspence.

Details

Summary

Resolves T9811.

Test Plan

Ran Drydock allocations, saw command failures show detailed standard output and error messages.

pasted_file (884×1 px, 291 KB)

(Ignore the exception stack trace showing in that screenshot; I did not include that in this diff)

Diff Detail

Repository
rP Phabricator
Branch
new-diff
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 8905
Build 10430: Run Core Tests
Build 10429: arc lint + arc unit

Event Timeline

hach-que retitled this revision from to Make it easier to diagnose command failures inside Drydock.
hach-que updated this object.
hach-que edited the test plan for this revision. (Show Details)
hach-que added a reviewer: epriestley.
hach-que edited edge metadata.
epriestley edited edge metadata.

See T9811. This is the broadest possible level of disclosure and I want to move forward with the narrowest possible level instead. It is not yet clear what that level is, but I suspect it is not the same as the broadest possible level.

(This change is also literally a giant copy/paste of 90% of its logic, but that's not really material.)

This revision now requires changes to proceed.Nov 22 2015, 10:11 PM