| commit | 0c0e815bdaf61a9ef6c1f5de319b13c21db5a9cc | [log] [tgz] |
|---|---|---|
| author | David 'Digit' Turner <digit@google.com> | Mon Mar 04 16:34:44 2024 +0100 |
| committer | CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 05 10:21:48 2024 +0000 |
| tree | d11f6196e674b62318b4f015af4c89c9348007ff | |
| parent | e3c78bba65e937b6a7aa286d9f045da331ce7412 [diff] |
Do not error-loop in case of missing or malformed build plan. This patch fixes an issue where enabling persistent mode and launching Ninja with a missing or malformed Ninja manifest would loop for about 1 minutes with a message like: ``` ninja: error: Error contacting server, falling back to local build: Connection refused ninja: error: Error contacting server, falling back to local build: Connection refused ninja: error: Error contacting server, falling back to local build: Connection refused ninja: error: Error contacting server, falling back to local build: Connection refused ``` This fixes the logic to correctly fall-back to a local build when this happens (in which case the line above is only printed once). This also makes the client connection loop more resilient to transient failures that can happen while trying to connect to a server that is going under shutdown, which resulted in random `Error contacting server` failures that could sometimes happen when running the regression tests. Fuchsia-Topic: persistent-mode Change-Id: I2a1d34f848144601a320c0b8eb6bbb3071df6ca5 Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/github.com/ninja-build/ninja/+/1001533 Reviewed-by: David Fang <fangism@google.com> Commit-Queue: David Turner <digit@google.com>
Ninja is a small build system with a focus on speed. https://ninja-build.org/
See the manual or doc/manual.asciidoc included in the distribution for background and more details.
Binaries for Linux, Mac and Windows are available on GitHub. Run ./ninja -h for Ninja help.
Installation is not necessary because the only required file is the resulting ninja binary. However, to enable features like Bash completion and Emacs and Vim editing modes, some files in misc/ must be copied to appropriate locations.
If you're interested in making changes to Ninja, read CONTRIBUTING.md first.
You can either build Ninja via the custom generator script written in Python or via CMake. For more details see the wiki.
./configure.py --bootstrap
This will generate the ninja binary and a build.ninja file you can now use to build Ninja with itself.
cmake -Bbuild-cmake cmake --build build-cmake
The ninja binary will now be inside the build-cmake directory (you can choose any other name you like).
To run the unit tests:
./build-cmake/ninja_test