Page MenuHomePhabricator

Fix Aphlict exit status
ClosedPublic

Authored by joshuaspence on Jan 21 2015, 7:34 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Apr 14, 9:48 PM
Unknown Object (File)
Sun, Apr 14, 9:48 PM
Unknown Object (File)
Sun, Apr 14, 9:48 PM
Unknown Object (File)
Sun, Apr 14, 9:47 PM
Unknown Object (File)
Sun, Apr 14, 9:42 PM
Unknown Object (File)
Sun, Apr 14, 8:57 PM
Unknown Object (File)
Thu, Apr 11, 10:05 AM
Unknown Object (File)
Mon, Apr 8, 4:51 PM
Subscribers

Details

Summary
Test Plan

Ran Aphlict and forced an error. Saw error messages in the logs and also saw a non-zero exit status.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

joshuaspence retitled this revision from to Fix Aphlict exit status.
joshuaspence updated this object.
joshuaspence edited the test plan for this revision. (Show Details)
joshuaspence added a reviewer: epriestley.
epriestley edited edge metadata.
epriestley added inline comments.
support/aphlict/server/aphlict_server.js
108–109

Do we need a return; here? This does not actually exit the process, does it?

Maybe renaming exit() to set_exit_code() or similar would be more clear.

This revision is now accepted and ready to land.Jan 21 2015, 2:44 PM

(In particular, I would expect --test to cause the server to start.)

support/aphlict/server/aphlict_server.js
108–109

Ah yeah, that seems correct.

joshuaspence edited edge metadata.

Rename exit() to set_exit_code()

This revision was automatically updated to reflect the committed changes.