No, we don't have a out-of-the-box way of doing it.
To answer 2), if ES is running it will "sweep" submissions without an
evaluation every ~2 minutes, and perform all necessary operations on them.
During a contest, CWS sends "notifications" (RPCs) to ES to notify it that
there is a new submission to compile, so the sweep is usually not doing
much, but cmsAddSubmission doesn't send this notification.
I don't think we have an example of a cmscontrib script that does RPCs, but
it shouldn't be hard to do one. If you are interested in writing a
cmsInvalidate and/or call EvaluationService.new_submission in
cmsAddSubmission, feel free to work on it. If you need some starting hints
let me know and I'll try to provide an example.
On 31 December 2017 at 13:07, Nir Lavee <nir692007@xxxxxxxxx> wrote:
Hi,
Very basic question, but I've looked for a while and couldn't find
anything:
Is there a way to invalidate a submission from the command line?
This would be useful for:
1) Partially automating task creation. When writing a task's parameters,
ideally I'd want to know the score of each solution, then fine tune the
time/memory/test data, and try again. Currently the easiest way to do this
is through AWS, but a command would be more powerful.
2) Complementing the functionality of cmsAddSubmission. It seems
submissions added this way are not always evaluated immediately (admittedly
I only did some basic tests. I'm using v1.3). In fact I'm not sure what
determines exactly when these submissions are evaluated. Any thoughts?
Thanks in advance,
Nir
