-
Notifications
You must be signed in to change notification settings - Fork 86
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
Reduce chance of save-jobs.ipynb
failing in CI
#2386
Conversation
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would 500 be reasonable? Idk how much of a difference it would make in performance
I actually didn't really notice much difference between 10 and 1000, just setting it to |
Sg, 1000 makes sense then. |
The problem is
service.jobs()
by default only gets the past 10 jobs. Usually this is fine, but there's a chance the past 10 jobs we've submitted have all been cancelled or have failed.This PR reduces the change of CI failing by increasing the number of jobs we collect. We can remove the limit by setting
limit=None
, but this takes too long to execute. I've picked 1000 as a compromise.This is ready for review, but don't merge until after #2382 is merged. When that happens, I'll pull main and re-run this notebook to update it.