commit | 86b32a64f596720313ff6515855f0bd8390dc452 | [log] [tgz] |
---|---|---|
author | jhorvitz <jhorvitz@google.com> | Fri Jun 18 12:55:04 2021 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Jun 18 12:56:28 2021 -0700 |
tree | 8d44bd9a04b7894a558542b3aed7a37addc6400b | |
parent | a7ac95b09b3220d5f6b14f961d7cbd9732fcb7e7 [diff] |
Include the Starlark stack trace as part of the crash's stack trace for all unhandled throwables originating in Starlark evaluation. In keeping with tradition of not wrapping `Error` in `AbstractParallelEvaluator`, different exception types are used for `RuntimeException` and `Error`. Additionally embed a context supplier in `StarlarkThread`. This is specifically targeted for the case of a crash during rule analysis, where the call stack itself doesn't include enough information to identify the rule (since the `BUILD` file is evaluated during loading). PiperOrigin-RevId: 380246681
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md