Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go ยป
No member browsing this thread
Thread Status: Active
Total posts in this thread: 1
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1085 times and has 0 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
App_info.xml users be warned if you see 197 (0xc5) EXIT_TIME_LIMIT_EXCEEDED error.

For What It's Worth: A post over at the BOINC.Dev forums , verbatim, which applies to those running with Anonymous platform which means they are using app_info.xml, noting that this is currently identified as exclusive to Seti, and of course is likely only affecting GPU crunchers!:
When you've updated to the latest and greatest (release candidate) (alpha) BOINC, coming from BOINC 7.0.28 or before, AND when crunching work on an anonymous platform GPU application (such as the ones from Lunatics), you have a good chance that all your work errs with a 197 (0xc5) EXIT_TIME_LIMIT_EXCEEDED error.

This is because of an addition to the code in BOINC 7.0.33, where when you run the anonymous platform and you have not supplied a flops value in your app_info.xml file, that the flops value used for GPU tasks is increased by a factor of 10.

It will only affect old work still in cache from before the upgrade. Any newer work your BOINC downloads, will not be affected.

Two ways to work around this:
1. Before you upgrade, set No New Tasks and run your cache empty. Report all. Then upgrade to the new version and set Allow New Tasks.

2. Done the upgrade with a full cache? Reset the project. This will throw away all present work in cache, but since the project has resend lost work available, your tasks will be resent to you and seen as new work.

[Mar 19, 2013 11:48:01 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread