Replies: 6 comments
-
In gradescope, there is a 120s timeout for each testcases |
Beta Was this translation helpful? Give feedback.
-
@KAIST-JongchanPark Thank you, looks like I have much work to do. I will close this for now. |
Beta Was this translation helpful? Give feedback.
-
Just FYI... |
Beta Was this translation helpful? Give feedback.
-
My implementation takes 98 seconds in virtual machine. Autograder in gradescope takes an eternity, however, it has been 20 minutes and still going. |
Beta Was this translation helpful? Give feedback.
-
@Rsln-M I managed to reduce the running time to 0.4s and only then would gradescope autograder pass. I think there are really large test cases. |
Beta Was this translation helpful? Give feedback.
-
Yes, I improved performance and it passed all test cases despite still taking a LOT of time. The testcases must be very large. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Name: Junyoung Lee
Hi all, I have 2 questions.
I've implemented the
crack
function, but the result of crackingyesterday.expected
has very slight errors. Here is my output:Has anyone else experienced these slight errors? If so, I would appreciate any guidance on which part of my code to fix.
Also, what should be the desired running time of
crack
? On my machine, crackingyesterday.expected
takes about 9 - 10 minutes. I wonder if my solution is efficient enough to pass Gradescope's autograder.Thank you.
Beta Was this translation helpful? Give feedback.
All reactions