successful API completeion but a null proxy list. Check
for the null instead of crashing.
client/
sysmon_win.cpp
svn path=/trunk/boinc/; revision=19221
to accept CPU, NVIDIA and ATI jobs.
These prefs are shown only where relevant:
e.g., only for processor types for which the project has app versions,
and if it has versions for only one type, no pref is shown.
These prefs affect both client and scheduler.
The client won't ask for work for a device blocked by prefs,
and the scheduler won't send it.
This replaces earlier optional project-specific prefs for
"no CPU jobs" and "no GPU jobs".
(However, these prefs continue to be honored on the server side).
- client: if NVIDIA driver is unknown, say that rather than 0
svn path=/trunk/boinc/; revision=19194
enforce "suspend if no recent input" and "exclusive apps"
only if overall mode if RUN_MODE_AUTO (run according to prefs)
svn path=/trunk/boinc/; revision=19193
ones already running.
The problem: we considered a job as started if it has an ACTIVE_TASK.
However, we were creating ACTIVE_TASKS for jobs before deciding
to run them, because we needed a place to store the coproc reservations.
This caused the above bug, and also had the undesirable effect
of creating slot directories before they're needed.
Solution: store coprocessor reservations in RESULT
rather than ACTIVE_TASK.
svn path=/trunk/boinc/; revision=19129
multithread apps overcommitted.
Actually: allow overcommitment but only a fractional CPU
(so that, e.g., we can run a GPU app and a 4-CPU app on a 4-CPU host)
svn path=/trunk/boinc/; revision=19126
"don't use GPUs while computer is in use" to
"don't use GPUs running graphics apps while computer is in use"
for NVIDIA GPUs.
NVIDIA's API for seeing if a GPU is running a graphics app
doesn't seem to reflect GPU use by the OS.
svn path=/trunk/boinc/; revision=19093
to whether job is already running.
This addresses a bug where several jobs are returned by sched RPC,
and one with a lexicographically greater name
happens to finish downloading first.
svn path=/trunk/boinc/; revision=19092
attribute is missing. That's the app's problem, not BOINC's
- sample assimilator: if a canonical instance has no output files,
rather than quitting create a file named WU_NAME_no_output_files
svn path=/trunk/boinc/; revision=19082
and <ati_backoff> elements to scheduler reply.
These specify backoffs for the resource types,
overriding the existing backoff mechanism.
Projects can supply these if they don't have apps of a particular type
and don't want to get periodic requests for them.
svn path=/trunk/boinc/; revision=19059
1) job finishes
2) job gets marked as "ready to report"
3) scheduler RPC is initiated
Hopefully this won't have an unintended side-effect
svn path=/trunk/boinc/; revision=19051
start only enough jobs to fill CPUs per project,
not all the CPU jobs at once.
I'm not sure how much difference this makes,
but this is how it's supposed to work.
- client: if app_info.xml doesn't specify flops,
use an estimate that takes GPUs into account.
- client: if it's been more than 2 weeks since time stats update,
don't decay on_frac at all.
svn path=/trunk/boinc/; revision=19035
use job name as tiebreaker if received times are the same.
This makes the order deterministic.
- web: show elapsed time and CPU time,
and show app version info, in result display
svn path=/trunk/boinc/; revision=19008
If you have 2 CPUs and a 1-day job in EDF mode,
the busy time should be zero, not .5 days.
Add a class BUSY_TIME_ESTIMATOR that makes a somewhat better
(though still fairly crude) estimate.
svn path=/trunk/boinc/; revision=19003
with a GPU request if project is anonymous platform
AND it has an app for that GPU type
- client: report overall work request as well as per-resource-type requests
svn path=/trunk/boinc/; revision=18994
Rom Walton