eb4445be6c
If we can't write to stdout we prefer to panic immediately rather than potentially lose logs we capture from redirecting stdout as a syslog backup. A unit test is included to verify the panic behaviour. Prior to the `log` diff in this branch the test failed because the non-nil `err` result from `fmt.Printf` was being away: ``` === RUN TestStdoutFailure === PAUSE TestStdoutFailure === CONT TestStdoutFailure FAIL github.com/letsencrypt/boulder/log 0.011s FAIL ``` After the `log` package diff in this branch is applied the test passes. I additionally tested this end-to-end by redirecting stdout to a full filesystem volume mounted into the Boulder docker image. It provoked the expected panic when a component tried to write to stdout and the filesystem was full. |
||
|---|---|---|
| .. | ||
| log.go | ||
| log_test.go | ||
| mock.go | ||