Hi EK,
I ran several tests on an earlier 0.6.0 version of core and it seems pretty stable. I did notice that when the miner switched to a job that hadn't been mined in a while that usually the first couple of POW were rejected due to the difficulty, but overall, seems like a good improvement.
I've made several last minute fixes to the miner and uploaded the latest changes to my github.
Great, I will keep testing, and trying to fix that isue that you described.
Do you have some simple steps how I could reproduce that problem? What is "in a while"?
I am still working on the "retarget testcase". I promise that I will fix the "duplicate" message today, when more than 20 POWs are in the queue rejecting the subsequent ones.
The steps to reproduce the issue are:
1) Create 2 jobs
2a) My jobs were simple so I waited for the bounties of the job I was mining to get claimed, then the miner automatically switched to the second job.
2b) You can also simulate this by canceling the first job.
The reason I can't be more specific about the occurrence was that I had other bugs I was working out, but I believe it may have something to do with how quickly you submit a POW after switching to the second job. Either way, just redo the steps above a couple times and I'm sure you'll see it.
but at least we bought some. 
