| commit | 718faed3dcd7663075aee6664b1282d464efd95b | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Fri Aug 02 13:24:19 2019 -0700 |
| committer | Tao Bao <tbao@google.com> | Fri Aug 02 13:36:49 2019 -0700 |
| tree | e5310cf112095a8aa8c735e1783cb774bddef2bf | |
| parent | c016c281c1f34aa2d9507cc8f2174b3ce52f4cbb [diff] |
releasetools: Don't write outputs if not in verbose mode. The change in [1] allows brillo_update_payload to write to stdout/stderr directly without buffering, to ensure dumping progress to screen continously. However, it now unconditionally writes to stdout/stderr even if caller doesn't specify `-v`. The behavior upsets PythonUnitTestResultParser in [2], which doesn't want any unexpected output from stderr for result parsing. This CL updates the logic to only give continous outputs in verbose mode. [1] commit 2f7e11ef27bc00108088eb2b0f5a5d9cc605afdd [2] https://android.googlesource.com/platform/tools/tradefederation/+/refs/heads/master/test_framework/com/android/tradefed/testtype/PythonUnitTestResultParser.java Test: Run ota_from_target_files.py with `-v`. Check there's continous output from brillo_update_payload. Test: `python -m unittest -v test_ota_from_target_files > /dev/null` doesn't show outputs from brillo_update_payload. Change-Id: I3b851203ef011a5b4d982948cf52793f6fb6ad2d
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.