-
Notifications
You must be signed in to change notification settings - Fork 70
Legacy HW1 grader reported spinning #96
Comments
last thing in log file was this:
|
I tried submitting Legacy HW1 reference solution to https://edge.edx.org/courses/course-v1:SUNY_Binghamton+CS445-2-S16+2016_Spring/courseware/64746ad0f2b84ce2af1f1b627c735866/ec766c87cbc7467b9a693078eb78d2c8/ and it span for five minutes so I restarted the grader |
this is the XML for that submission element: <problem>
<coderesponse queuename="cs169-rev-production">
<filesubmission points="100"/>
<codeparam>
<grader_payload>
{"assignment_name": "assignment5-legacy-bugfix",
"assignment_spec_uri": "[email protected]:saasbook/hw-refactoring-legacy-code-bug-fix-ci.git",
"autograder_type": "HW5Grader",
"due_dates": {"2016-016-30": 1.0, "2016-06-06": 0.75}
}
</grader_payload>
</codeparam>
</coderesponse>
</problem> and I notice a mis-formatting in the due dates ... |
I fixed that issue, re-published, re-started the grader and resubmitted. Then saw this error in the grader output:
|
so I think the date was still invalid. See http://stackoverflow.com/questions/800118/ruby-time-parse-gives-me-out-of-range-error - now that I changed the due dates like so: "due_dates": {"2016-06-30": 1.0, "2016-06-06": 0.75} i.e. with a valid month the grader seems to work normally: |
So the action item here then is to make the grader handle this failure state a little more gracefully ... |
logged in to the grader and saw this error:
The text was updated successfully, but these errors were encountered: