-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
Nightly Build Failure 2024-11-12 #3958
Comments
I ran the following:
I started and stopped this before it completed, but it seemed to be working as expected and set up this draft and created the following logs
So my read on this is that it was an intermittent Zenodo bork, not a major API change or structural problem. If this is still a problem tomorrow, I'll re-investigate. |
Thanks for investigating further! Getting a 500 back does point to "problem is on Zenodo's end" vs. an API change that would in theory kick out a 400. 🤞 |
The Zenodo step of last night's nightly build (2024-11-15) and the Nightly build
Full stack trace
v2024.11.0 release
Zenodo deposition logs
Full stack trace
|
Yes, if you see the response input it shows it made a query to the existing deposition and got a 500 error, which it is then trying to shunt into |
The error 500 that we're getting on the Sandbox server doesn't happen until after all of the files have been uploaded, and we don't get that far with the deposition on the Production server because of the timeouts, so it seems possible that even without the timeouts, we'll get the same problem on the production server. But also Zenodo has been bad about synchronizing the behavior of the two servers so who knows. |
Attempting to re-run the Zenodo data release
|
Last night (2024-11-17) two different builds kicked off within half an hour of each other. One was a Logs from Zenodo data release on main
This one had several uploads with retries before one of them finally failed. Maybe we should be more generous with the number of retries? Logs from Zenodo data release on nightly-build-cruft
|
I emailed Zenodo support about the consistent timeouts today (2024-11-18) |
We've had one successful nightly sandbox deployment and several successful fast ETL sandbox deployments so maybe this is back to working magically? If it passes tomorrow morning 2024-11-20 I'll close. |
We got another successful sandbox release last night, and Zenodo Support responded saying that they made a faulty deployment to the Sandbox on Nov 12th that could have created issues, so I'm going to call this fixed for the moment. 🤞🏼 |
Overview
What do you think happened, if anything?
Something funky going on with the Zenodo API. Getting a 500 back when trying to get the latest record. Also they just updated
master
yesterdayThis is important to fix ASAP since we're going to try to do the quarterly release this week.
Next steps
Verify that everything is fixed!
Once you've applied any necessary fixes, make sure that the nightly build outputs are all in their right places.
Tasks
Relevant logs
Google Batch
link to build logs from internal distribution bucket
The text was updated successfully, but these errors were encountered: