We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This issue was originally TRAC 10794
Original Reporter: @MarcusNoble
If many runs have run with the wrong reduction variables its could be laborious to go through each one and re-run them with the correct variables.
It would be nice to be able to perform a batch re-run by selecting all desired runs and then entering the variables once.
Considerations needs to be made to prevent this monopolising the systems time and resources. (Possible a priority option?)
http://activemq.apache.org/how-can-i-support-priority-queues.html
If priority queues are used there may need to be changes made to how the messages are consumed.
Keywords: AUTOREDUCTION
AutoReduction issue closed and moved to autoreduce repo during ticket migration.
The text was updated successfully, but these errors were encountered:
@NickDraper (2015-04-27T08:10:35): Moved to R3.5 at the R3.4 code freeze
Sorry, something went wrong.
lottiegreenwood
No branches or pull requests
This issue was originally TRAC 10794
Original Reporter: @MarcusNoble
If many runs have run with the wrong reduction variables its could be laborious to go through each one and re-run them with the correct variables.
It would be nice to be able to perform a batch re-run by selecting all desired runs and then entering the variables once.
Considerations needs to be made to prevent this monopolising the systems time and resources. (Possible a priority option?)
http://activemq.apache.org/how-can-i-support-priority-queues.html
If priority queues are used there may need to be changes made to how the messages are consumed.
Keywords: AUTOREDUCTION
AutoReduction issue closed and moved to autoreduce repo during ticket migration.
The text was updated successfully, but these errors were encountered: