Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Repo cloning fails with LFS bandwidth quota limit reached. #56

Open
sogartar opened this issue Dec 11, 2024 · 3 comments
Open

Repo cloning fails with LFS bandwidth quota limit reached. #56

sogartar opened this issue Dec 11, 2024 · 3 comments
Assignees
@ScottTodd
Labels
bug Something isn't working

Comments

@sogartar
Copy link 

git clone [email protected]:iree-org/iree-test-suites.git

Error downloading object: sharktank_models/llama3.1/assets/toy_llama.irpa (37f90b4): Smudge error: Error downloading sharktank_models/llama3.1/assets/toy_llama.irpa (37f90b4754197b1e732c43010e3979223136d91f8c843998aa376afc8c997d09): batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.

I am not sure if this is intended and what is the best practice when working with Git LFS. I actually don't want to resolve and download all files under LFS if I don't have to.
@ScottTodd ScottTodd self-assigned this Dec 11, 2024
@ScottTodd
Copy link
Member

I'm still figuring out how to set up billing and add a data pack to increase our LFS budget.

In the meantime...

I am not sure if this is intended and what is the best practice when working with Git LFS. I actually don't want to resolve and download all files under LFS if I don't have to.

Per https://stackoverflow.com/a/42021818, it looks like setting the GIT_LFS_SKIP_SMUDGE environment variable will skip fetching LFS files if you have LFS installed, like this:

GIT_LFS_SKIP_SMUDGE=1 git clone SERVER-REPOSITORY

If you don't have LFS installed then a standard git clone should work fine.

@ScottTodd ScottTodd mentioned this issue Dec 11, 2024
Merged
@ScottTodd ScottTodd added the bug Something isn't working label Dec 11, 2024
ScottTodd added a commit to iree-org/iree that referenced this issue Dec 11, 2024
@ScottTodd
Skip test_sharktank job until quota issues are fixed. (#19458)
f9210a8 
This job will fail until we get more quota for git LFS.

Context: iree-org/iree-test-suites#56

Sample errors:
https://github.com/iree-org/iree/actions/runs/12278845603/job/34262001578
```
Fetching LFS objects
  /usr/bin/git lfs fetch origin c644a9dfc3e5e1a9d071d5e786b79cf612e9b1d3
  fetch: Fetching reference c644a9dfc3e5e1a9d071d5e786b79cf612e9b1d3
  batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.
  Error: error: failed to fetch some objects from 'https://github.com/iree-org/iree-test-suites.git/info/lfs'
  The process '/usr/bin/git' failed with exit code 2
```

ci-exactly: build_packages, test_sharktank
@sogartar
Copy link
Author

@ScottTodd, thank you for the suggestion.
The step that failed was the branch checkout after the clone. I am not sure what is going on, but after the failed clone I did

git reset --hard

and it seems it resolved the references.

@ScottTodd
Copy link
Member

If anyone sees errors when pushing (even to a fork) like this:

git push scotttodd sharktank-docs

Pushing to https://github.com/ScottTodd/iree-test-suites.git
Uploading LFS objects:   0% (0/6), 0 B | 0 B/s, done.
batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.
error: failed to push some refs to 'https://github.com/ScottTodd/iree-test-suites.git'

Run the push with --no-verify. See https://stackoverflow.com/questions/36626793/disable-git-lfs-for-a-remote

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ScottTodd ScottTodd

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sogartar @ScottTodd