Sorry for that, my child was born two months ago so I'm not working on the problems this year. Also, I was on parental leave and missed this thread. Anyway, my fault.
*tl;dr: I'm working on a fix to allow the commandline tool to accept problems with any kind of I/O sets. I think it will be ready for Round 3.* Half of the fix is done which is exposing the required data in the server. The other half, updating the commandline tool to use this new information, is complete but it requires some extra testing. The issue was that it assumed that all problems have exactly one small and one large I/O set when parsing the user status and submissions. Did you try using the -f flag? That flag skips the checks that use that information and tries to submit directly. The new version will not make any kind of assumptions about the I/O sets, so it should be more robust. The only assumption it will make is that the only kind of inputs are small and large, which I hope will be more persistent. On Saturday, April 14, 2012 9:25:51 PM UTC-7, Vexorian wrote: > > I had a couple of issues with the tool during the qualification. Wondering > if it was just me or if anyone else experienced them. > > I was surprised it did not have any issue downloading and submitting > problem A, as it has a different format and all that. > > When I tried to solve B, I was able to download B-small and B-large, but > it would not let me upload. It said that I did not download the test case > before uploading, so I had to submit manually. The same happened with C. I > did not even try with D-small. > -- You received this message because you are subscribed to the Google Groups "Google Code Jam" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-code/-/XzpiEfHbsWAJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code?hl=en.
