I am unable to reproduce whatever runtime errors are encountered on google's servers even with the same runtime environment they claim to use.
I've even re-written one problem in multiple languages and get the same vague "run time error, test case skipped" message. If it were timing out or overrunning memory then I would get a different error. Extremely frustrating. I've even generated test data to the specs listed in the large and hidden sets and can not reproduce. I am hoping that at the very least some of these issues will be brought to light to allow for smoother code submission in future rounds, and I would be curious to see their test sets. Even with P3's insidious edge case, which to be honest I missed during competition, testing with that after the fact on my code submissions did not yield a runtime error but would have yielded a wrong answer instead. P2's general solution is very easy to implement, and I don't see how this case could have produced a runtime error either. I admit I was clueless about a sane approach for p4 and the interactivity is a neat twist as I have not competed in many years. I hate submitting my code for server evaluation, although I suppose this makes the contest accessible to all. I wonder if the reasons behind the change would preclude making both styles available to future contestants. -- You received this message because you are subscribed to the Google Groups "Google Code Jam" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-code/8787eeff-f027-466f-8efc-8805ed159e39%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
