Tests of internal mechanisms

There is definitely something wrong with the actual Python 2.5 implementation.
It seems that there are different implementations used on different servers.
Please have a look at my submissions 5357523 and 5357524. The code I submitted is exactly the same, but runtime and memory usage differ significantly. Standard runtime for a Python program that does nothing more than starting the interpreter used to be 0.03 s for Python 2.5 and memory usage used to be 3.7 MB. This is congruent to my submission 5357523. But submission 5357524 takes 0.18 s and 4.4 MB for exactly the same code.

Same problem with Python 3 installation. Two submissions of the same code:
Submission 5357623: AC in 0.91 s with 5.6 MB mem
Submission 5357624: AC in 2.64 s with 6.6 MB mem

Another one: The Python 3.x installation lacks the random module. See my submissions
5357566 (AC) and 5357567 (NZEC) - same code, but random module imported (and not used!).

I can absolutely confirm this. Something must have happend. The results do significantly differ with identical code.

I don't know what this statement refers to, but the Python problems still exist.
- Python 3.1 has no random module available
- Runtimes for both Python 2.5 and Python 3.1 seem to be stable, now, but to the worse:
Python 2.5 needs about 0.15 s and 4.4 MB mem just for startup compared to 0.02-0.03 s and 3.7 MB mem which was typical before.
I don't understand why the former Python 2.5 installation that worked fine, cannot be left as it was?

I made a contest (spoj.pl/NOOBSIAM) but the judging never ends --> spoj.pl/NOOBSIAM/status/

Hi,

I'm attempting to run a Java solution to LITE through the judging system but it keeps returning NZEC. From what I understand, NZEC on Java submissions only occur when an exception is thrown from the main method. However, even if I have the code swallow all exceptions (submission 5475631) I get the NZEC.
Can someone check that it is not a problem with the judging system?

thanks!

Thanks for the fix. I saw the submission is now reported as TLE: has it been rerun? Was the problem that TLE was reported as NZEC? How come the time reported earlier was ~2.5s, now a TLE, while I see a Java submission by someone else to the same problem that was ~6s?

I recently revieved several emails from SPOJ for solutions I posted in December of 2010. I don't know if that has anything to do with the testing being done or not.

I solved problem spoj.pl/problems/QCJ1/
my submission id 5506253 shows to be solved in .01 time however on resubmitting the same code the time gets changed. Once to .03 and once to .04.
Kindly look into it.

Thanks,
jayesh02

It's not a bug.
The time unfortunately depends not only on algorithm but also on traffic on SPOJ.
For example if You submit a program and somebody's just getting TLE You'll have somehow slower program than submitting it when nobody's online (which's ofc not possible ).

Python 3.1 still has no random module available, it's curious for me ; it should be included.
Thanks.

I have had a couple of instances of the wrong problem ID appearing in the submit form
after using the 'edit' link from the status page. The last occurrence was using the edit link
for my submission 6204220. It took me back to the submit page but the problem ID was
TEST instead of ASSIST

Pls help, my submission with ID 6765418 got internal error on problem INCSEQ spoj.pl/problems/INCSEQ/