Better port 6.12.28, Lars as 6.12.26 contains a big bug towards the account manager BAM!
That one's fixed in 6.12.28

And version numbers?

(I'd mostly quote Richard:)

You too. {slap} :)

I have the feeling it has to do with how opening a second BOINC Manager has changed...

Version 7.0 has been released.

BOINC Monitor wrote:

Version 7.0 - Added graphics.

OK, I am trying to understand this...

• Belgium (thigorin - BOINC dev, no team's member (yet?)),
  
• Ireland (Чигорин - SETI@home, Team U. S. ARMY),
  
• Luxembourg (Gugel - QMC@HOME, Team US Navy),
  
• Switzerland (Administrator - ABC@home, Team NATO),
  
• Switzerland (GPUHOV - Enigma@Home, Team SwissTeam.NET)
  

and who knows where else...

Peter

Does anyone see the BOINC manager exit dialog?

Just to be sure, what are your log_flags?

25/05/2011 19:50:05 |  | log flags: file_xfer, sched_ops, task, benchmark_debug, checkpoint_debug
25/05/2011 19:50:05 |  | log flags: cpu_sched, dcf_debug, file_xfer_debug, sched_op_debug, statefile_debug

I'll tell later when I'm again behind the machine. [...] I suspect that "file_xfer" could be missing on that machine. I'll check then when back there. (But I'd not ever remove it intentionally. I've been downgrading BOINC on the machine step-by-step to 6.10.32 and then back to 6.12.26, but I also hope that neither the installer nor older client would touch cc_config.xml?)

Just to be sure, what are your log_flags?

25/05/2011 19:50:05 |  | log flags: file_xfer, sched_ops, task, benchmark_debug, checkpoint_debug
25/05/2011 19:50:05 |  | log flags: cpu_sched, dcf_debug, file_xfer_debug, sched_op_debug, statefile_debug

bool PERS_FILE_XFER::poll() {
   ...
   if (log_flags.file_xfer) {
       msg_printf(
           fip->project, MSG_INFO, "Finished %s of %s",
           is_upload?"upload":"download", fip->name
       );
   }
   ...
}

Dust in your eyes? ;-)

23-Apr-2011 10:33:05 [WUProp@Home] Started download of wu_1303317104_23653
23-Apr-2011 10:33:06 [WUProp@Home] Finished download of wu_1303317104_23653

Backing off 22 min 10 sec on download of 
Backing off 19 min 24 sec on upload of 
[cpu_sched] Request CPU reschedule: files downloaded

Not sure what you mean?

11176 PrimeGrid 2011-05-31 5:13:03 PM Started upload of pps_sr2sieve_21291464_1_0
11177 PrimeGrid 2011-05-31 5:13:04 PM Finished upload of pps_sr2sieve_21291464_1_0

• You are using 6.12.26 and it still seems to request new tasks prior to uploading finished ones: [...] I'm not sure when this was finally fixed (if really already?), could you try 6.12.28 for this?
  

• Could you replace your screenshot with another one, which would include the "Remaining time" column? This would show the amount of cached/available work.
  
• You are using 6.12.26 and it still seems to request new tasks prior to uploading finished ones:

  11173 PrimeGrid 2011-05-31 5:13:01 PM Computation for task pps_sr2sieve_21291464_1 finished
  11174 PrimeGrid 2011-05-31 5:13:01 PM Sending scheduler request: To fetch work.
  11175 PrimeGrid 2011-05-31 5:13:01 PM Requesting new tasks for NVIDIA GPU
  11176 PrimeGrid 2011-05-31 5:13:03 PM Started upload of pps_sr2sieve_21291464_1_0
  11177 PrimeGrid 2011-05-31 5:13:04 PM Finished upload of pps_sr2sieve_21291464_1_0
  11178 PrimeGrid 2011-05-31 5:13:15 PM Scheduler request completed: got 1 new tasks

  I'm not sure when this was finally fixed (if really already?), could you try 6.12.28 for this?
  
• Now with 6.12.26, if you manually update PrimeGrid after having uploaded a finished result, does it get some more tasks, or not?
  
• What is (e.g. just now) your available amount of work (sum of their remaining times) separately for CPU, nVidia, ATI?
  

Peter

David Anderson wrote:

The client doesn't exit until the 15 seconds is up.

The Collatz problem is something different. I checked in a change that might fix it.

[trac]changeset:23619[/trac]?

Well, there is that infinite QCN task at 9519%.

The problem is a history that updates to quickly, I will change that in the next version.

Go to BT settings and remove the check at "Smart mode".
This setting only works with projects that behave properly.
Not with projects that are >= 100% or have an invalid time left.

Well, there is that infinite QCN task at 9519%.
[...]
edit: Ha, suspended the QCN task and the refreshing immediately switched to 30 seconds that I'd changed it to. Then when resuming the task history kept updating at 30 second intervals for a little, then reverted to the 1 second order.

Update: Seems that the History screen is being updated every second no matter the setting, 120, 119..., pulsing then at 15% load, which is eating the CPU time [v 1.03]

Also have a strange bug which only manifests on W7-32, client 6.10.25 and 26, don't know if this was a problem with previous clients. Cannot suspend a task through BT, but it works via the standard BM. Tasks that are waiting to run or running can be suspended. When selecting a "running" or "waiting to run" task and combine this with a Ready to Start task (RtS), then the RtS will suspend, but suspect that is because the task is run for a fraction of a second before suspending during the multi-task selection suspend. Reversing to select a suspended tasks not yet started does not work, but when already started it does.