ccf36aa928
On the build servers, LOG_DIR is a subset of DIST_DIR, which encodes the build number. This means that LOG_DIR is guaranteed to be different for every build, and we'll never re-use previous soong runs on CI builds. The current use case (writing out soong metrics) shouldn't care if the value changes, so pipe the environment variable through, bypassing the env dep checks. It's not clear if this is the only issue triggering soong_build re-runs on the build servers, but it's a start. Test: Change DIST_DIR, soong_build does not re-run. Change-Id: I59bf117f3fbc0e7f10f0506d3d1ac7564c6a00dc |
||
---|---|---|
.. | ||
dep_fixer | ||
diff_target_files | ||
extract_apks | ||
extract_jar_packages | ||
extract_linker | ||
fileslist | ||
go2bp | ||
host_bionic_verify | ||
javac_wrapper | ||
merge_zips | ||
multiproduct_kati | ||
path_interposer | ||
pom2bp | ||
pom2mk | ||
run_with_timeout | ||
sbox | ||
soong_build | ||
soong_ui | ||
symbols_map | ||
zip2zip | ||
zipsync |