Better handling for exceptions in destinations - fixes #45

[itamarst]

Fixes #45.

[coveralls]

Coverage increased (+0.02%) to 99.32% when pulling e43ec03 on sending-exceptions-45 into e6b4ae7 on master.

[coveralls]

Coverage increased (+0.02%) to 99.32% when pulling e43ec03 on sending-exceptions-45 into e6b4ae7 on master.

[wallrj]

Ah, the penny drops! So exceptions raised in failing destinations are logged to the working destinations.
Perhaps it'd be nice to demonstrate that the order of the destinations is unimportant ie failures in destinations further down the list will be logged to working destinations earlier in the destination list.

[itamarst]

It's not "working destinations", it's "all destinations".

[itamarst]

Re-read tests, I think coverage implicitly does what you want in later test.

[wallrj]

Thanks @itamarst

Notes:

• Tests all pass locally with a single warning /home/richard/projects/HybridLogic/eliot/eliot/tests/test_action.py:526: DeprecationWarning: Action should be initialized with a TaskLevel action = Action(logger, "uuid", "/1/2/", "sys:me") which may or may not be expected.
• Merged forward and re-ran tests - they all passed.
• Ran Flocker test suite using this branch of Eliot (merged forward). There were errors, but none related to Eliot.

Points:

1. travis-ci shows a few other warnings which may warrant followup issues: https://travis-ci.org/ClusterHQ/eliot/builds/56744628

WARNING: 'default' html theme has been renamed to 'classic'. Please change your html_theme setting either to the new 'alabaster' default theme, or to 'classic' to keep using the old default.

/home/travis/build/ClusterHQ/eliot/.tox/pypy/site-packages/setuptools/dist.py:292: UserWarning: The version specified ('0.6.0-22-g0fcbad3') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details.
(versioneer upgrade maybe?)

WARNING: html_static_path entry u'/home/travis/build/ClusterHQ/eliot/docs/source/_static' does not exist
(I mentioned that one before)

1. Might be nice to document the handling of exceptions during serialisation and when writing to destinations.

Please address or answer these and the inline comments above and merge when you're satisfied with the build results.

[itamarst]

I will fix two of the issues mentioned above (sphinx theme, versioneer) and then do release when Travis is happy.

[coveralls]

Coverage increased (+0.01%) to 99.34% when pulling b618d6a on sending-exceptions-45 into 6646d6a on master.