I checked in a fix for this. -- David Rytis Slatkevičius wrote: > Hello all, > I'm working on a project which is non-cpu-intensive and does not have result > files (instead, all network communication is done by the app itself). This > causes an interesting phenomenon when a workunit finishes: > > *20:29:27 AProject Computation for task pinger_15571_0 finished > 20:29:27 AProject Sending scheduler request: To fetch work. > 20:29:27 AProject Requesting new tasks > 20:29:32 AProject Scheduler request completed: got 1 new tasks > 20:29:35 AProject Starting pinger_15796_0 > 20:29:35 AProject Starting task pinger_15796_0 using pinger version 103 > 20:29:43 AProject Sending scheduler request: To report completed tasks. > 20:29:43 AProject Reporting 1 completed tasks, not requesting new tasks > 20:29:48 AProject Scheduler request completed* > > As you can see, a task finishes and immediately a scheduler request is done, > because there is no more work in the queue, however, the WU that has > finished hasn't yet reached ready_to_report state, so it is not reported. > Instead, it is reported on a separate sched request, as soon as the first > scheduler request (to fetch new work) is completed. > > This would be fine if we were doing file uploads, because then the workunit > would not be ready_to_report until the file upload was complete, but in this > case there is no file upload. > > Tested with 6.2.19, 6.6.36, 5.10.45 - same issue, although it does not > always manifest itself. Some users have it more often, some don't at all. >
_______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
