Closed GoogleCodeExporter closed 9 years ago
64bits support is still in beta level, post the solution cause problem please.
Original comment by newsc...@gmail.com
on 21 Jun 2011 at 1:58
if you are chinese speaker ,contact me with QQ im ,my account is 10982766
Original comment by newsc...@gmail.com
on 21 Jun 2011 at 2:00
It doesn't depend from the solution, if a solution stuck at compiling stage and
i rejudge it, the solution is not going to stuck ( the compiling is ok on
rejudge ).
I did some test, 10 solution I rejudge at same time, all this 10 times ( the
same solution 10 times) , the result was 30 of 100 where stuck at compiling
stage, the running parameter is 2 ( 2 cores cpu ) and sleep time is 5. I have
attach an image of the result.
I am not a chinese speaker, thanks for replaying.
Original comment by fatonmeh...@gmail.com
on 21 Jun 2011 at 7:19
Attachments:
it seems that your runX(run0~run4) dirs is not fullfilling your OJ_RUNNING
settings in /home/judge/etc/judge.conf.
check this link,pls
http://code.google.com/p/hustoj/wiki/MultiRUNNING
Original comment by newsc...@gmail.com
on 21 Jun 2011 at 10:59
I try the wiki ( step by step ) with (OJ_RUNNING = ) 1, 2, 3, 4, 5 running
solution but still the same problem.
Original comment by fatonmeh...@gmail.com
on 22 Jun 2011 at 8:36
that is strange, you might want to contact me with gtalk, my gmail account is
newsclan@gmail.com .
Original comment by newsc...@gmail.com
on 23 Jun 2011 at 8:50
r1071 may fix this problem
this bug may affect centos and ubuntu 64-bits
Original comment by newsc...@gmail.com
on 23 Jun 2011 at 12:42
finally(hope so),r1073
Original comment by newsc...@gmail.com
on 24 Jun 2011 at 9:57
Original comment by newsc...@gmail.com
on 15 Jul 2011 at 2:20
Original issue reported on code.google.com by
fatonmeh...@gmail.com
on 18 Jun 2011 at 9:41