Forum

I registered for the CodeFu competition coming up this weekend and I wanted to get a feel for the programming environment you have set up on the website, so I fired up the Practise Round 1 problems and started working on the 100p problem. As soon as I hit the compile button, I got a strange-looking java exception - weird considering that I wrote all my code in c++ This happened both in the new arena and in what I'm assuming to be the old system.

So I tried reopening the arena a couple of times and the code eventually compiled, only to give "incorrect result" for all test cases. So I copied the code into a local editor and I got correct results for all the test cases I tried.

I believe you may have some serious issues with the grading system. Any help would be welcome.

The testing system, especially for C# and C++, has been modified these days. There have been some known bugs and performance issues that we believe that are done now. If you have tested your problem in the meanwhile, you may have gotten continuous weird results. Nevertheless, that was expected.

So, give it a try again. If the problem persists, let us know.

Now my code passes 83 out of a 100 test examples, the other 17 report the following: "Exception occured when executing test.java.io.IOException". Considering I'm not using java... These are by far the weirdest exceptions I've ever gotten

I hope the testing system will be up and running properly for tomorrow's competition. Cheers!

Ok I just retested and it worked just fine now. Thanks for your help.

I submitted a solution to the 500p problem in the same problem set and I got the same problem again: "Exception occured when executing test.java.io.IOException".

Ok this is really weird... In 3 compile & test runs, once it reported a java exception, once reported wrong results and once reported correct results all round... :S

The reported Java exception means a runtime exception in your C++ solution. This is not a bug, but a fix requirement for some next version.

About the three different outcomes, are they on the same solution?

Yes, they were... I don't recall changing anything... The three test runs were 2 days apart though.

I believe that there should be a FAQ or something for this kind of errors - I had to learn that cout calls cause a java exception by myself... It would be nice at least to include a warning when the submission contains forgotten cout calls... My 2 cents...