Exit Codes
These exit codes are returned from a Buck command to the shell when the command exits.
These exit codes are Buck's binary protocol for interacting with other software such as shell scripts.
Note that in the case of some fatal errors—such as FATAL_OOM, FATAL_IO, or FATAL_DISK_FULL—Buck itself might not be able to reliably detect the source of the failure. If this occurs, Buck falls back to reporting FATAL_GENERIC.
0 | SUCCESS | The command returned successfully. No errors. No warnings. |
1 | BUILD_ERROR | Build resulted in a non-specific user error. |
2 | BUSY | Buck daemon is busy processing another command. For more information, see Buck Daemon (buckd). |
3 | COMMANDLINE_ERROR | Incorrect user-supplied command-line options. For more information, see Common Parameters or the topic page for the specific command that you executed. |
4 | NOTHING_TO_DO | Nothing to build or evaluate for the specified command. |
5 | PARSE_ERROR | Error in parsing the build file or in constructing the target or action graph. |
6 | RUN_ERROR | Failure while running a binary or installing a binary on a device. For more information, see buck run. |
10 | FATAL_GENERIC | Generic non-recoverable internal error. |
11 | FATAL_BOOTSTRAP | Non-recoverable error in Buck bootstrapper. |
12 | FATAL_OOM | Non-recoverable out-of-memory (OOM) error. |
13 | FATAL_IO | Generic non-recoverable I/0 error. |
14 | FATAL_DISK_FULL | No space on storage device. |
32 | TEST_ERROR | Test run had user-specific test errors. For more information, see buck test. |
64 | TEST_NOTHING | There were no tests to run. For more information, see buck test. |
130 | SIGNAL_INTERRUPT | Command was interrupted (Ctrl + C) |