Total hashrate erroneous when one job fails

[mccurls]

Problem: Total hashcount for any given attack is taken from the last known hashrate per agent/job. In this case, one job failed (error code 255 and not much else of note) and the hashrate for that failed job did not return to '0'.

Job Failed Error

cuEventDestroy(): unspecified launch failure

cuEventDestroy(): unspecified launch failure

cuStreamDestroy(): unspecified launch failure

cuModuleUnload(): unspecified launch failure

cuModuleUnload(): unspecified launch failure

> Error: exit status 255

The wordlist attack shows the following:

Whilst the totals are shown below:

[lachlan2k]

Fixed in e47ceb6fbc7f32a393ba29db45cb14c596b9f25e

Now, the total shows only the hashrate of running jobs.

This does mean, however, once an attack is completely finished, it's not easy to see what your hashrate was (as it'll display as 0), but I think it makes sense to only ever show the hashrate of running jobs.