Quote from: lukasbradley on December 17, 2012, 07:19:23 PM

Quote from: kakobrekla on December 17, 2012, 06:29:58 PM

Quote from: lukasbradley on December 17, 2012, 05:07:51 PM

Quote from: lukasbradley on December 17, 2012, 05:29:17 AM

Looking good so far on 1.60 on MMQs. It's been running stably for 3 hours now on 2 miners.

I'm going to guess this was the change that did it:

Code:

Give RingWrapper.currentJob its own separate lock

I'll let everyone know more tomorrow morning if it stays up all night.

I spoke too soon... it died. Ugh... what a bad night.

Will rewrite the shell script tonight to try to use the new command line args.

Can you send a log to email?

kakobrekla

I will, but it's the same issue as before. The process continues to report on the miner, but the miner apparently stops. Hashing drops to zero over 3 or so minutes.

Ok, just to make sure this is the second 1.60 with shasum of 689d00e5ac86cabfde749ac11a912ec35a27bf54? If it is, lets wait for ET to go through the log.