sapling/eden
Stanislau Hlebik 3193f4fab3 mononoke: fail with non-zero exit code in serve_forever if failure happened
Summary:
Previously our jobs would have exit with error code 0 even if there was an
actual error. The reason for this was because error was just ignored (or rather
just printed to stderr).
This is not a huge problem but it makes tw output confusing - it shows that
the task was "Completed" while in reality it "Failed"

Reviewed By: ahornby

Differential Revision: D20693297

fbshipit-source-id: 4f615e2ef11f2edbb9bdbcf49cb1635929fdae89
2020-04-17 14:57:56 -07:00
..
benchmarks Migrate from TAsyncSocket 2020-03-31 13:20:02 -07:00
docs add EdenServer recovery step and recover after failed takeover data send handshake 2020-04-07 09:52:21 -07:00
fs Remove unnecessary calls to add RSRoutingHandler 2020-04-16 14:26:09 -07:00
integration relax checking of C++ type formatting in an integration tests 2020-04-15 17:58:12 -07:00
locale add a copyright header to glibc_en.po 2019-04-26 14:38:27 -07:00
mononoke mononoke: fail with non-zero exit code in serve_forever if failure happened 2020-04-17 14:57:56 -07:00
scm filesystem: move rust walker to it's own file 2020-04-16 16:51:21 -07:00
scripts Tidy up license headers 2019-10-11 05:28:23 -07:00
test_support implement our own temporary file management during integration tests 2020-04-13 13:12:04 -07:00
test-data enable treemanifest in snapshots 2019-08-28 18:46:03 -07:00
third-party fix some macOS build warnings 2020-01-23 17:37:39 -08:00
win flip EDEN_WIN_NOMONONOKE to EDEN_HAVE_MONONOKE 2019-08-27 17:04:19 -07:00
.gitignore eden: wire up mac contbuild 2019-02-05 21:52:30 -08:00
Eden.project.toml Eden.project.toml file for Nuclide 2018-04-26 11:05:23 -07:00