| Age | Commit message (Collapse) | Author |
|---|
|
to be behind trunk.
`tox -e py27` passes full test suite. Now to work on replacing mocker.
|
|
I had previously asked for this, but we're hoping to handle it in a
more generic way. Just because we receive a signal doesn't mean that
all logging is broken.
The more general solution we'll chase is to catch a failure of a log
message and fall back if necessary across the board. That way cloud-init
will still send logging to the right places on a user interupt.
|
|
|
|
the signal information in one block instead of many.
|
|
|
|
handle those signals more gracefully and
with better messaging than what comes builtin.
|
