Yes, we also observed timeouts with 220611. To mitigate the issues, we have reduced the task size to 50% in the new app version 220612. We'd appreciate if you try it out. We'll investigate all issues.

220612 is an improvement but there is more to be done.

The majority of tasks now complete (on my hosts) at 2 hours or just after and all of those validate. [Have seen other hosts that regularly do them quicker and slower.]
I have also seen tasks that ran for 3, 4 or 5 hours that also completed and validated, they also received the appropriate credit for the longer run time.

However there are some tasks that run for the full 10 hours that then complete with the message "task loda reached time limit 36000".
Some of these tasks have been marked as 'Validate error' and got no credit but others have been marked as valid and given credit, the problem with these is that the credit is only equivalent to what a 2 hour task would have received, ie a fifth of what they should have received. In view of that I have taken to aborting tasks (when I have the opportunity) that I think (hope) might not finish before the 36000 timeout is reached. The hope is that another 1, 2 or even 3 tasks might run in that time that do get the appropriate credit. The practice isn't sustainable and the issue needs to be fixed please.

There is also the problem with the 'Error while computing' message (EXIT_CHILD_FAILED) but they are more environmental and have probably been happening since the project started. I think they are mostly down to user configuration issues with their own systems but I suspect some of them may also be due to problems at the server end, possibly network issues. I rarely get them but I see others with quite a lot.

Yes, we also observed timeouts with 220611. To mitigate the issues, we have reduced the task size to 50% in the new app version 220612. We'd appreciate if you try it out. We'll investigate all issues.

220612 is an improvement but there is more to be done.

The majority of tasks now complete (on my hosts) at 2 hours or just after and all of those validate. [Have seen other hosts that regularly do them quicker and slower.]
I have also seen tasks that ran for 3, 4 or 5 hours that also completed and validated, they also received the appropriate credit for the longer run time.

However there are some tasks that run for the full 10 hours that then complete with the message "task loda reached time limit 36000".
Some of these tasks have been marked as 'Validate error' and got no credit but others have been marked as valid and given credit, the problem with these is that the credit is only equivalent to what a 2 hour task would have received, ie a fifth of what they should have received. In view of that I have taken to aborting tasks (when I have the opportunity) that I think (hope) might not finish before the 36000 timeout is reached. The hope is that another 1, 2 or even 3 tasks might run in that time that do get the appropriate credit. The practice isn't sustainable and the issue needs to be fixed please.

There is also the problem with the 'Error while computing' message (EXIT_CHILD_FAILED) but they are more environmental and have probably been happening since the project started. I think they are mostly down to user configuration issues with their own systems but I suspect some of them may also be due to problems at the server end, possibly network issues. I rarely get them but I see others with quite a lot.

I haven't had the time limit of 36,000 second yet but I had another 3 of the time limit reached of 11,159.30 seconds,
which was the error I was receiving with the .10 versions.

Conan

I suspect that these timeouts were caused by a combination of two thIngs: 1) the “iterate” mining profile was used, which consumes more cpu flops than others, 2) you have a very fast cpu.

We have disabled the “iterate” profile, which should fix the problem on your machine (you may need to cancel old WUs)