exit on error Command Line flag #273
Labels
Comments
ghost
assigned
elad661
pushed a commit
that referenced
this issue
May 31, 2013
Exit on every core failure, even network disconnect. This is mostly useful for the automated test-suite we are working on. Fixes issue #273
embolalia
added a commit
that referenced
this issue
Mar 25, 2015
Intentionally introducing a regression to simplify the config work. This reopens #273. When we're actually remotely close to having a plan for that automated testing, we'll redo something like this (probably in a better way).
|
Not sure if this is needed for testing, we're currently able to test a large portion of the bot without actually starting a full instance. |
|
If nobody is running the bot to test it, and need this, I think we can close it for now (this comment is not sponsored by the Clean Up Industry, I swear). |
|
The way testing works now, I agree we don't need this feature. (Thanks for checking old issues, @Exirel!) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As suggested by @elad661 for #268
"Run its own willie instance so that we can easily detect commits that breaks the ability of the bot to start and connect. To do that we will need to add a switch willie, something like
--exit-on-errorto make the bot exit with a predefined code as soon as a core exception is detected."The text was updated successfully, but these errors were encountered: