Page MenuHomePhabricator

Fix Aphlict exit status
ClosedPublic

Authored by joshuaspence on Jan 21 2015, 7:34 AM.
Tags
None
Referenced Files
F18803739: D11456.diff
Sat, Oct 18, 3:24 AM
F18751003: D11456.id27541.diff
Sat, Oct 4, 9:31 AM
F18748460: D11456.id27555.diff
Fri, Oct 3, 10:45 PM
F18659162: D11456.id.diff
Tue, Sep 23, 10:14 AM
F18658231: D11456.id27555.diff
Tue, Sep 23, 5:26 AM
F18637278: D11456.diff
Sep 17 2025, 6:51 AM
F18628790: D11456.id27555.diff
Sep 16 2025, 7:18 AM
F18627356: D11456.diff
Sep 16 2025, 3:47 AM
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
Branch
master
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 3980
Build 3993: [Placeholder Plan] Wait for 30 Seconds

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.