Charlie, we probably need to do a systematic check that the terminology is
consistent throughout.
You committed most of the intel (or intel_gpu) code in a 'first pass' on Dec 5,
2012: Rom changed a large number of instances when hooking it up to the server
on Dec 8, 2012, but I'm guessing this one got missed.
https://github.com/BOINC/boinc/commit/ce87ec9848643a094337f67f78a1d5077cf7f772
https://github.com/BOINC/boinc/commit/516eff60b045a1d916f2be3e47e0857c1efbe364
On Thursday, 24 August 2017, 8:10, Charlie Fenton
wrote:
A quick look at the code makes me believe it is a bug. looking at GIT Master,
in client/log_flags.cpp, CC_CONFIG::parse_options_client() has on lines 414-415:
if (xp.parse_int("ignore_intel_dev", n)) {
ignore_gpu_instance[PROC_TYPE_INTEL_GPU].push_back(n);
but in lib/cc_config.cpp, CC_CONFIG::write() has on lines 626-630:
for (i=0; i I don't know if this is an actual bug or not, but it is something that has
> been happening for a couple of years through various versions of the BOINC
> manager/client. If one explicitly ignores the Intel iGPU via the
> cc_config.xml (0), said option will
> disappear from the file after several days. I haven't been able to pin down
> exactly how long the option exists in the file prior to removal. The option
> last appeared in the event log on 19 Aug. I was in the event log this
> evening to look at something else and noticed that the option is no longer
> being logged. I've reinserted the option and will keep a closer eye on it.
>
> Even though the Intel iGPU is ignored implicitly via the global preferences,
> I choose to also have it explicitly in the cc_config.xml. My question is
> this a bug and should this be investigated?
___
boinc_alpha mailing list
boinc_al...@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.