11 Commits

Author	SHA1	Message	Date
Cole Helbling	fc3cf4ecb2	RunCommandLogs: identify and access via uuid ... Using a sha1 of the command combined with the build ID is not a particularly good or unique identifier: * A build could fail, be restarted, and then succeed -- assuming no configuration changes, the sha1 hash of the command as well as the build ID will be the same. This would lead to an overwritten log file. * Allowing user input to influence filenames is not the best of ideas.	2022-01-31 08:58:33 -08:00
Graham Christensen	dcb0c1425c	RunCommandLogs: set a UUID automatically	2022-01-31 08:58:33 -08:00
Graham Christensen	cf49a05ff5	RunCommandLogs: add a uuid to each log entry	2022-01-31 08:58:33 -08:00
Janne Heß	796ce165d4	RunCommand: Allow displaying command output	2022-01-28 13:03:15 -08:00
Graham Christensen	a7aeb766aa	RunCommandLogs: add a helper for if it failed with an exec error	2022-01-07 15:05:33 -05:00
Graham Christensen	d849856dcd	RunCommandLogs: add helpers for if it is running/failed/signaled	2022-01-07 15:05:33 -05:00
Graham Christensen	c81acbf93e	RunCommandLogs: test recording a signaled process without a core dump	2022-01-07 15:05:33 -05:00
Graham Christensen	d003fec8a5	RunCommandLogs: add a did_succeed helper	2022-01-07 15:05:33 -05:00
Graham Christensen	5bb3e2be78	Record the errno if exec fails	2022-01-07 15:05:33 -05:00
Graham Christensen	4ce8239cea	RunCommand: create run logs for each execution	2022-01-07 15:05:33 -05:00
Graham Christensen	52843195db	RunCommandLogs: init table	2022-01-07 15:05:33 -05:00