| commit | 2f8f5dd0f6ef971301ffbcf7528fc63e293ff0a0 | [log] [tgz] |
|---|---|---|
| author | Jim Pollock <jmpollock@chromium.org> | Fri Apr 30 23:14:52 2021 +0000 |
| committer | Commit Bot <commit-bot@chromium.org> | Sun May 02 10:47:20 2021 +0000 |
| tree | 31e55739427e88ea40785947a1b7ced86735ddda | |
| parent | a69a9e160ff4db6cd8971d30d023aae1379a5c9a [diff] |
Revert "nn: use cryptohome daemon storage location for cache files" This reverts commit a69a9e160ff4db6cd8971d30d023aae1379a5c9a. Reason for revert: Has broken relesae builds: https://logs.chromium.org/logs/chromeos/buildbucket/cr-buildbucket.appspot.com/8848535058247719152/+/steps/BuildPackages/0/stdout Original change's description: > nn: use cryptohome daemon storage location for cache files > > This CL forces any request that sets up compilation caching to store > the files in the cryptohome daemon storage location of the ml_service > process. This is done due to the docs indicating that cache files should > be stored in a secure location. See: > https://source.android.com/devices/neural-networks/compilation-caching#security > > We can't do this in configuration since the daemon storage is per-user > and the username hash needs to be queried at runtime. > > BUG=b:178762478 > TEST=FEATURES=test emerge-volteer aosp-frameworks-ml-nn > > Change-Id: I09d5d4be01a3435cedda4e822a4f423f8723e5ce > Reviewed-on: https://chromium-review.googlesource.com/c/aosp/platform/frameworks/ml/+/2817759 > Tested-by: Jim Pollock <jmpollock@chromium.org> > Auto-Submit: Jim Pollock <jmpollock@chromium.org> > Commit-Queue: Jim Pollock <jmpollock@chromium.org> > Reviewed-by: Stuart Langley <slangley@chromium.org> > Reviewed-by: Michael Pishchagin <mblsha@google.com> Bug: b:178762478 Change-Id: Iac9913c54332c5fb5f1205d7b6ed9c58825b866c Reviewed-on: https://chromium-review.googlesource.com/c/aosp/platform/frameworks/ml/+/2859271 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by: David Riley <davidriley@chromium.org> Commit-Queue: Jim Pollock <jmpollock@chromium.org> Auto-Submit: Jim Pollock <jmpollock@chromium.org>