| commit | 46901fb8cadc6ea94922f8ae36fed012b58b595a | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Tue Nov 06 10:26:21 2018 -0800 |
| committer | Tao Bao <tbao@google.com> | Tue Nov 06 10:42:35 2018 -0800 |
| tree | 9f960660aa5960066f9ea7ec2afcfc32d1cc04df | |
| parent | a0a7e03ff00563545d1fc57df12f82ed16a9e138 [diff] |
releasetools: Log the exceptions before rethrowing.
In Append2Simg and Append in verity_utils.py, we catch and rethrow
exceptions as BuildVerityImageError. However, this suppresses the
traceback from the original exception which usually indicates the actual
cause. We can better handle this with the raise statement in Python 3,
which is however unavailable in Python 2.
This CL logs the exception before rethrowing to retain the useful bits.
Test: Inject an error to append2simg. `m -j systemimage` with
aosp_marlin-userdebug. Check the output.
Change-Id: I0c2f57d6023fa1038256b85fa98d57ad0244a70d
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.