You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 4, 2024. It is now read-only.
Hey folks, I have a scenario in which I will have two different flows (with different sets of tests btw) in the same repo.
One is much faster then the other (thus why we want to segregate them).
I've thought about having "two queues with different priorities", which is almost the same as sending PRs with different priorities anyway.
But one drawback of using priority is that i will disrupt the current running batch.
So, my question is: Is there a way to use priority (let's say p=0 and p=1) so that PRs with "p=1" (or batches with p=1) doesn't cancel the current running batch (with p=0)?
The text was updated successfully, but these errors were encountered:
Hi @notriddle, I have zero experience with Elixir (even less with bors codebase), can you give me some hints/directions where should I look for in the codebase to propose such change?
Hey folks, I have a scenario in which I will have two different flows (with different sets of tests btw) in the same repo.
One is much faster then the other (thus why we want to segregate them).
I've thought about having "two queues with different priorities", which is almost the same as sending PRs with different priorities anyway.
But one drawback of using priority is that i will disrupt the current running batch.
So, my question is: Is there a way to use priority (let's say p=0 and p=1) so that PRs with "p=1" (or batches with p=1) doesn't cancel the current running batch (with p=0)?
The text was updated successfully, but these errors were encountered: