Changes between Initial Version and Version 3 of Ticket #512


Ignore:
Timestamp:
Dec 11, 2007, 8:21:41 AM (16 years ago)
Author:
Nicolas
Comment:

Fix some formatting.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #512 – Description

    initial v3  
    11Since the beginning of november (first noticed there), the cpu time update in the client doesn't work anymore under linux with our app. When downgrading the boinc libs of our client app to for example rev. 13231, it works again.
    22
    3 I added this line to boinc_checkpoint_completed in boinc_api.C:1010 [[BR]]
    4 fprintf(stderr,"in Checkpoint complete: cur_cpu = %g, last_wu = %g, last checkp = %g\n",cur_cpu,last_wu_cpu_time,last_checkpoint_cpu_time);[[BR]]
     3I added this line to boinc_checkpoint_completed in boinc_api.C:1010
     4{{{
     5fprintf(stderr,"in Checkpoint complete: cur_cpu = %g, last_wu = %g, last checkp = %g\n",cur_cpu,last_wu_cpu_time,last_checkpoint_cpu_time);
    56(before) update_app_progress(last_checkpoint_cpu_time, last_checkpoint_cpu_time);
     7}}}
    68
    7 and this one to timer_handler: 852[[BR]]
     9and this one to timer_handler: 852
     10{{{
    811fprintf(stderr,"cur cpu = %g, initial_wu_cpu_time=%g , last_wu = %g , last_checkpoint = %g\n",cur_cpu,initial_wu_cpu_time,last_wu_cpu_time,last_checkpoint_cpu_time);
    912(also before) update_app_progress(last_wu_cpu_time, last_checkpoint_cpu_time);
    10 
    11 From this I got the output: [[BR]]
    12 cur cpu = 0, initial_wu_cpu_time=0 , last_wu = 0 , last_checkpoint = 0 [[BR]]
    13 in Checkpoint complete: cur_cpu = 58.4437, last_wu = 58.4437, last checkp = 58.4437 [[BR]]
    14 cur cpu = 0, initial_wu_cpu_time=0 , last_wu = 0 , last_checkpoint = 58.4437 [[BR]]
     13}}}
     14From this I got the output:
     15{{{
     16cur cpu = 0, initial_wu_cpu_time=0 , last_wu = 0 , last_checkpoint = 0
     17in Checkpoint complete: cur_cpu = 58.4437, last_wu = 58.4437, last checkp = 58.4437
     18cur cpu = 0, initial_wu_cpu_time=0 , last_wu = 0 , last_checkpoint = 58.4437
     19}}}
    1520
    1621So for me this sounds like boinc_worker_thread_cpu_time() sometimes works and sometimes doesn't.
    … …  
    1823
    1924A slight guess at what could have produced this behaviour is this changeset:[[BR]]
    20 http://boinc.berkeley.edu/trac/changeset/13880/trunk/boinc/api/boinc_api.C
     25[13880/trunk/boinc/api/boinc_api.C]