-
Notifications
You must be signed in to change notification settings - Fork 612
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate GCS files to new (ideally public) locations #18518
Comments
Until we find a better location, let's at least download and then upload mirrors to Azure for the riscv and arm files ( |
@Eliasj42 could you help mirror the I'm less concerned about the |
Like this? |
Yep, then point the code to the new file locations. |
Updated several links to point to files in azure shark-public container instead of gcp. Progress on #18518. Signed-off-by: Elias Joseph <[email protected]> Co-authored-by: Elias Joseph <[email protected]>
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. |
See #18518. These tests have started failing since the GCS bucket is now returning 403 errors.
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 Add tests for TFLite models iree-test-suites#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 #18238.The text was updated successfully, but these errors were encountered: