8875baf99d
The bloaty here was compiled with this patch: https://github.com/google/bloaty/pull/149 Hopefully that lands upstream and we can track master again. This adds BuildStats.+Debug because we need symbols to get sensical data. Bloaty's WASM support is experimental and currently doesn't support having a stripped (Release) version be profiled using the symbols of a Debug version. This means that the buildStats for debug will be higher than actual, but hopefully the absolute positioning will be the same and thus the outputs useful. Bug: skia: Change-Id: Id7bf721843e8c52a0aae2b7e57ff95397693b3dd Reviewed-on: https://skia-review.googlesource.com/c/163256 Reviewed-by: Mike Klein <mtklein@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com> |
||
---|---|---|
.. | ||
android_ndk_darwin | ||
android_ndk_linux | ||
android_ndk_windows | ||
android_sdk_linux | ||
armhf_sysroot | ||
bloaty | ||
cast_toolchain | ||
chromebook_arm_gles | ||
chromebook_x86_64_gles | ||
clang_linux | ||
clang_win | ||
cmake_linux | ||
gcloud_linux | ||
go | ||
go_deps | ||
linux_vulkan_sdk | ||
lottie-samples | ||
mesa_intel_driver_linux | ||
mips64el_toolchain_linux | ||
moltenvk | ||
node | ||
opencl_headers | ||
opencl_intel_neo_linux | ||
opencl_ocl_icd_linux | ||
procdump_win | ||
protoc | ||
scripts | ||
skimage | ||
skp | ||
svg | ||
valgrind | ||
win_ninja | ||
win_toolchain | ||
win_toolchain_2015 | ||
win_vulkan_sdk | ||
__init__.py | ||
asset_utils_test.py | ||
asset_utils.py | ||
assets.py | ||
README.md |
Assets
This directory contains tooling for managing assets used by the bots. The primary entry point is assets.py, which allows a user to add, remove, upload, and download assets.
Assets are stored in Google Storage, named for their version number.
Individual Assets
Each asset has its own subdirectory with the following contents:
- VERSION: The current version number of the asset.
- download.py: Convenience script for downloading the current version of the asset.
- upload.py: Convenience script for uploading a new version of the asset.
- [optional] create.py: Script which creates the asset, implemented by the user.
- [optional] create_and_upload.py: Convenience script which combines create.py with upload.py.
Examples
Add a new asset and upload an initial version.
$ infra/bots/assets/assets.py add myasset
Creating asset in infra/bots/assets/myasset
Creating infra/bots/assets/myasset/download.py
Creating infra/bots/assets/myasset/upload.py
Creating infra/bots/assets/myasset/common.py
Add script to automate creation of this asset? (y/n) n
$ infra/bots/assets/myasset/upload.py -t ${MY_ASSET_LOCATION}
$ git commit
Add an asset whose creation can be automated.
$ infra/bots/assets/assets.py add myasset
Add script to automate creation of this asset? (y/n) y
$ vi infra/bots/assets/myasset/create.py
(implement the create_asset function)
$ infra/bots/assets/myasset/create_and_upload.py
$ git commit