From 993de69baf544df5011277f3d9f90a5e381cd3cd Mon Sep 17 00:00:00 2001
From: David Anderson <davea@ssl.berkeley.edu>
Date: Fri, 2 Dec 2005 19:38:29 +0000
Subject: [PATCH] non-CPU-intensive fix

svn path=/trunk/boinc/; revision=9021
---
 checkin_notes        |  7 +++++++
 client/app_control.C |  9 +++++----
 doc/test_matrix.php  | 19 ++++++++++++++-----
 3 files changed, 26 insertions(+), 9 deletions(-)

diff --git a/checkin_notes b/checkin_notes
index 2f59454431..ae578f6683 100755
--- a/checkin_notes
+++ b/checkin_notes
@@ -14123,3 +14123,10 @@ David  1 Dec 2005
 
     client/
         cs_scheduler.C
+
+David  1 Dec 2005
+    - core client: don't make all tasks non-CPU-intensive
+        (from John McLeod)
+
+    client/
+        app_control.C
diff --git a/client/app_control.C b/client/app_control.C
index 1875acae41..7fed2d3428 100644
--- a/client/app_control.C
+++ b/client/app_control.C
@@ -863,10 +863,11 @@ bool ACTIVE_TASK::get_app_status_msg() {
     parse_double(msg_buf, "<fpops_cumulative>", result->fpops_cumulative);
     parse_double(msg_buf, "<intops_per_cpu_sec>", result->intops_per_cpu_sec);
     parse_double(msg_buf, "<intops_cumulative>", result->intops_cumulative);
-    parse_int(msg_buf, "<non_cpu_intensive>", new_non_cpu_intensive);
-    if (new_non_cpu_intensive != non_cpu_intensive) {
-        non_cpu_intensive = new_non_cpu_intensive;
-        gstate.request_schedule_cpus("Change in app CPU-intensive status");
+    if (parse_int(msg_buf, "<non_cpu_intensive>", new_non_cpu_intensive)) {
+        if (new_non_cpu_intensive != non_cpu_intensive) {
+            non_cpu_intensive = new_non_cpu_intensive;
+            gstate.request_schedule_cpus("Change in app CPU-intensive status");
+        }
     }
     return true;
 }
diff --git a/doc/test_matrix.php b/doc/test_matrix.php
index 0b53bfd426..9553717db0 100644
--- a/doc/test_matrix.php
+++ b/doc/test_matrix.php
@@ -10,6 +10,9 @@ For each release, please do
 <li> The general tests
 <li> As many of the other test groups as possible.
 </ol>
+If you have experienced problems with BOINC that are not
+exercised by any of these tests,
+please post to the <a href=http://www.ssl.berkeley.edu/mailman/listinfo/boinc_alpha>boinc_alpha@ssl.berkeley.edu</a> email list.
 
 <h3>General tests</h3>
 
@@ -33,10 +36,6 @@ Verify that output file is uploaded,
 that the result is reported,
 and that new work is downloaded and started.
 
-<li> Exit BOINC in the middle of a long file download.
-Note the fraction done.
-Restart BOINC.
-Verify that download resumes from the same point.
 
 <li> Suspend/resume features:
 suspend and resume results,
@@ -59,6 +58,15 @@ Make sure client and manager start up OK.
     and make sure work is downloaded and started.
 </ul>
 
+<h3>File transfer restart</h3>
+<ul>
+<li> Exit BOINC in the middle of a long file download.
+Note the fraction done.
+Restart BOINC.
+Verify that download resumes from the same point.
+<li> Same, upload.
+</ul>
+
 <h3> Preferences tests</h3>
 <ul>
 <li> Test 'don't run when user active' preference.
@@ -97,9 +105,10 @@ Make sure client and manager start up OK.
 </ul>
 <h3>Tests for modem-connected computers</h3>
 <ul>
-<li> Do General Tests from a modem-connected computer.
+<li> Do General Tests from a modem or ISDN-connected computer.
 <li> Test 'confirm before connect' preference.
 <li> Test 'Disconnect when done' preference.
+<li> Do these tests with both single-user and Service-mode install (Windows).
 </ul>
 <h3>Tests for computers with personal firewalls</h3>
 <li> Do General tests on a computer that uses a personal firewall