Just seen in 7.6.21

15/12/2015 02:10:10 | SETI@home | Requesting new tasks for AMD/ATI GPU
15/12/2015 02:10:10 | SETI@home | [sched_op] CPU work request: 0.00
seconds; 0.00 devices
15/12/2015 02:10:10 | SETI@home | [sched_op] AMD/ATI GPU work request:
167077.55 seconds; 0.00 devices
15/12/2015 02:10:13 | SETI@home | Scheduler request completed: got 0 new
tasks
15/12/2015 02:10:13 | SETI@home | [sched_op] Server version 707
15/12/2015 02:10:13 | SETI@home | No tasks sent
15/12/2015 02:10:13 | SETI@home | No tasks are available for AstroPulse v7
15/12/2015 02:10:13 | SETI@home | Tasks for CPU are available, but your
preferences are set to not accept them
15/12/2015 02:10:13 | SETI@home | Tasks for NVIDIA GPU are available, but
your preferences are set to not accept them
15/12/2015 02:10:13 | SETI@home | Tasks for Intel GPU are available, but
your preferences are set to not accept them
15/12/2015 02:10:13 | SETI@home | This computer has reached a limit on
tasks in progress
15/12/2015 02:10:13 | SETI@home | Project requested delay of 303 seconds


The clincher is "This computer has reached a limit on tasks in progress",
but instead of putting that out as answer to the work request, we first
have the (confusing?) "tasks are available for X but you don't want those"
messages.
Since this is a server decision to not send any further work because it has
a maximum limit in place, can't we get a log alike this:

15/12/2015 02:10:10 | SETI@home | Requesting new tasks for AMD/ATI GPU
15/12/2015 02:10:10 | SETI@home | [sched_op] CPU work request: 0.00
seconds; 0.00 devices
15/12/2015 02:10:10 | SETI@home | [sched_op] AMD/ATI GPU work request:
167077.55 seconds; 0.00 devices
15/12/2015 02:10:13 | SETI@home | Scheduler request completed: got 0 new
tasks
15/12/2015 02:10:13 | SETI@home | [sched_op] Server version 707
15/12/2015 02:10:13 | SETI@home | No tasks sent
15/12/2015 02:10:13 | SETI@home | This computer has reached a limit on
tasks in progress
15/12/2015 02:10:13 | SETI@home | Project requested delay of 303 seconds

-- Jord van der Elst.
_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to