Open ScottTodd opened 2 months ago
Until we find a better location, let's at least download and then upload mirrors to Azure for the riscv and arm files (qemu-aarch64
, toolchain_iree_manylinux_2_28_20231012.tar.gz
, and any others)
@Eliasj42 could you help mirror the https://storage.googleapis.com/iree-shared-files/qemu-aarch64
and toolchain_iree_manylinux_2_28_20231012.tar.gz
files to the sharkpublic Azure storage account or some other public location? We can find a better long term home for those files later.
I'm less concerned about the .tflite
files. We can just disable any tests relying on those.
toolchain_iree_manylinux_2_28_20231012.tar.gz
Like this? https://sharkpublic.blob.core.windows.net/sharkpublic/GCP-Migration-Files/qemu-aarch64 https://sharkpublic.blob.core.windows.net/sharkpublic/GCP-Migration-Files/toolchain_iree_manylinux_2_28_20231012.tar.gz
Yep, then point the code to the new file locations.
There are still a few places to update. A user just noted that the links in https://github.com/iree-org/iree/blob/main/build_tools/riscv/riscv_bootstrap.sh are dead.
We should also still switch to easier to manage files (git lfs?) with reproducible steps for generating them, instead of just mirroring to a cloud bucket that some project members have access to.
We depend on a few files hosted in a GCP project using various buckets.
Most uses can be discovered in this repo with a regex search of
https://storage\.googleapis\.com.*iree
:.tflite
files like those iniree-model-artifacts
could be fetched from https://www.kaggle.com/models/ (formerly TFHub / TensorFlow Hub). Better yet, tests for TFLite can be moved to https://github.com/iree-org/iree-test-suites (see https://github.com/iree-org/iree-test-suites/issues/5).mnist_train_test
is pretty bespoke and could be ported to https://github.com/iree-org/iree-test-suites or https://github.com/iree-org/iree-experimental/.jpeg
files could be stored in git (license permitting) or downloaded from a third party location instead of hosting our own mirror. Or we could just use fake test dataThose files are (as far as I can tell) only read from. They aren't written to, outside of very rare maintenance (none in the last year IIRC). There is a bucket that is read-write, used for ccache:
http://storage.googleapis.com/iree-sccache/ccache
. We are in the process of migrating off of that in https://github.com/iree-org/iree/issues/18238.