-
Notifications
You must be signed in to change notification settings - Fork 2
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
Downloading > 1 GiB files from buildomat fails some (most?) of the time #36
Comments
I believe I might've hit this on a job today? |
That might have a different underlying cause; |
I have (finally) redone the downloading logic a bit here for two reasons:
We'll get log messages like this, now, if there's an interrupted connection:
I have tested interrupting and resuming downloads fairly extensively using Either way, I think we need to start trying to do this routinely again now that the instrumentation is in place so that we can catch it again if it's still occurring. |
Running into issues downloading |
This happened to me downloading from
Just wanted to note this here in case having a timestamp is useful (this error is from a few minutes before I posted this). |
@jgallagher What URL would you have been downloading at the time? |
Huh, this is exciting!
So the interruption appears to have been somewhere in here:
I have some things I can tweak, at least, to improve things here. Thanks for the heads up! |
Hit the same issue
|
Were you able to resume the download with range requests? |
I was yesterday, yeah. Looks like Laura was using the same script I was:
|
Yes, I ran the script again and it completed |
Attempting to curl this URL from
atrium
https://buildomat.eng.oxide.computer/wg/0/artefact/01H8QBDTBWH4XS1ZSXBP9N47V7/Telf7HF0eNoZK443nD4ykEv6gbv3tqvhvPvFZXEae2g7yxZp/01H8QBFKMQ9VYJDS1M45Q66ZAY/01H8QJ02TAB8APZPVY7262W2Z4/repo-pvt1.zip fails some of the time at almost exactly 1 GiB:It doesn't always fail, particularly from the lab, but it seems to usually fail from outside the lab. From @jmpesp:
@augustuswm (on this exact URL) and @leftwo (on different buildomat URLs pointing to artifacts of similar size) also reported similar errors.
The text was updated successfully, but these errors were encountered: