summaryrefslogtreecommitdiff
path: root/test
diff options
context:
space:
mode:
authorSimon MacMullen <simon@rabbitmq.com>2015-02-26 14:54:58 +0000
committerSimon MacMullen <simon@rabbitmq.com>2015-02-26 14:54:58 +0000
commitdb0aaf821c7f41810bd7f2a452205548633355b4 (patch)
tree201effa65b02da24f2a57197323c43d0b42c2d9d /test
parentcfc289b72cfc2619b4694fe13fa100c64d328018 (diff)
downloadrabbitmq-server-git-db0aaf821c7f41810bd7f2a452205548633355b4.tar.gz
Detangle boot error handling, step 2
We used to have a weird situation where an error inside a boot step would cause us to go through error logging twice. The exception would get caught in run_step/3, then go through boot_error() etc, and basic_boot_error/3 would exit again, leading to more stuff being logged as an application start failure. So to fix that, let's exit with a special atom which prevents further logging. Also rename functions to be a bit more meaningful.
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions