-
Notifications
You must be signed in to change notification settings - Fork 157
Feat; job_queue table definition & mark a request as complete if all jobs are finished #2200
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
base: master
Are you sure you want to change the base?
Feat; job_queue table definition & mark a request as complete if all jobs are finished #2200
Conversation
cca4e3d
to
3e1489a
Compare
…jobs are finished
3e1489a
to
d0ed82f
Compare
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.
Did a quick scan and left a bunch of comments, but it would likely be best to discuss this at our call.
target TEXT NOT NULL, | ||
backend TEXT NOT NULL, | ||
benchmark_set INTEGER NOT NULL, | ||
collector_id TEXT NOT NULL, |
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.
We finally got to a place where we need collectors, let's merge #2157 first then, so that we can use a proper foreign key here.
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.
Good idea, I've updated that PR
…benchmark set made into a a struct
job_queue
table.job_queue
.benchmark_request
as complete if all jobs associated with the request have the status ofsuccess
orfailure
.I've omitted
job_splitting
as this PR is modestly big. However, bar marking things as complete, the PR is fairly mechanical.