BUG Report: 3rd result don't validate, because the 1st & 2nd result validated already

Author	Message
Sutaru Tsureku Volunteer tester Send message Joined: 6 Apr 07 Posts: 7105 Credit: 147,663,825 RAC: 5	Message 1854026 - Posted: 9 Mar 2017, 8:24:40 UTC Last modified: 9 Mar 2017, 8:28:33 UTC AFAIK, this happen since a few years... No solution possible? 1st and 2nd WU send out. 1st result came. 2st result missed the deadline. A 3rd WU send out. Now the 2nd result come after deadline. 1st and 2nd result validate. 3rd result come and get an invalid. Example: http://setiathome.berkeley.edu/workunit.php?wuid=2429434010 Workunit 2429434010 name ap_19no09ab_B0_P0_00281_20170210_21323.wu application AstroPulse v7 created 11 Feb 2017, 5:00:39 UTC canonical result 5503955182 granted credit 574.94 minimum quorum 2 initial replication 2 max # of error/total/success tasks 5, 10, 10 Task click for details - Computer - Sent - Time reported or deadline explain - Status - Run time (sec) - CPU time (sec) - Credit - Application 5503955182 - 7203873 - 11 Feb 2017, 5:00:46 UTC - 13 Feb 2017, 6:18:15 UTC - Completed and validated - 34,040.02 - 32,969.24 - 574.94 - AstroPulse v7 Anonymous platform (CPU) 5503955183 - 7468551 - 11 Feb 2017, 5:00:45 UTC - 8 Mar 2017, 8:23:04 UTC - Completed and validated - 160,243.22 - 81,087.37 - 574.94 - AstroPulse v7 v7.00 x86_64-pc-linux-gnu 5567860620 - 8021868 - 8 Mar 2017, 5:00:48 UTC - 8 Mar 2017, 11:03:29 UTC - Completed, marked as invalid - 564.59 - 168.47 - 0.00 - AstroPulse v7 Anonymous platform (ATI GPU) Is this 'just' an AP thing, or this happens also with MB (SETI) results? Thanks. BTW. No, no... ;-) My AMD Radeon R9 Fury X VGA cards use still Crimson 15.12 with 1912.5 driver in it - software/drivers after make invalid AP results... - because of my experiences with tests of all (7) software/drivers after up to Crimson 16.3.2. ID: 1854026 ·

rob smith Volunteer moderator Volunteer tester Send message Joined: 7 Mar 03 Posts: 22182 Credit: 416,307,556 RAC: 380	Message 1854032 - Posted: 9 Mar 2017, 8:43:18 UTC This is a "feature" - if the second party is late in returning, but does so before the third party they do get included in the validation process (I think there is a time limit on how late they can be - this is to allow for computers that only contact the servers at infrequent intervals rather than continuously.) Your result was returned after the validator had done its run between the first two, thus your result was "late" - the second party returned about three hours before you did. Without looking carefully at the outputs it is hard to see if your result was "significantly different" to the other two results, which might explain why the result was declared "invalid". Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? ID: 1854032 ·

Sutaru Tsureku Volunteer tester Send message Joined: 6 Apr 07 Posts: 7105 Credit: 147,663,825 RAC: 5	Message 1854043 - Posted: 9 Mar 2017, 10:19:54 UTC Last modified: 9 Mar 2017, 10:28:28 UTC Here are the results... Because for better overview - uninteresting I have made very small (not readable). If interested - copy it to e.g. Notepad and it's displayed in readable size. 1st result: Task 5503955182 Name ap_19no09ab_B0_P0_00281_20170210_21323.wu_0 Workunit 2429434010 Created 11 Feb 2017, 5:00:43 UTC Sent 11 Feb 2017, 5:00:46 UTC Report deadline 8 Mar 2017, 5:00:46 UTC Received 13 Feb 2017, 6:18:15 UTC Server state Over Outcome Success Client state Done Exit status 0 (0x00000000) Computer ID 7203873 Run time 9 hours 27 min 20 sec CPU time 9 hours 9 min 29 sec Validate state Valid Credit 574.94 Device peak FLOPS 0.00 GFLOPS Application version AstroPulse v7 Anonymous platform (CPU) Peak working set size 21.98 MB Peak swap size 18.02 MB Peak disk usage 5.04 MB Stderr output <core_client_version>7.6.33</core_client_version> <![CDATA[ <stderr_txt> Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64 CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX AstroPulse v7 Windows x64 rev 2692, V7 match, by Raistmer with support of Lunatics.kwsn.net team. by Lunatics team. Built with uncommitted modifications state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64 CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX ### Restart at 47.02 percent. state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64 CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX ### Restart at 47.02 percent. state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64 CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX ### Restart at 47.97 percent. state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64 CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX ### Restart at 47.97 percent. state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64 CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX ### Restart at 50.56 percent. state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64 CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX ### Restart at 50.56 percent. state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64 CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX ### Restart at 50.56 percent. state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64 CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX ### Restart at 52.53 percent. state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64 CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX ### Restart at 52.53 percent. state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64 CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX ### Restart at 61.60 percent. state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64 CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX ### Restart at 62.22 percent. state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64 CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX ### Restart at 64.13 percent. state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64 CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX ### Restart at 67.06 percent. state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64 CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX ### Restart at 71.28 percent. state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64 CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX ### Restart at 82.26 percent. state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 single pulses: 0 repetitive pulses: 0 percent blanked: 8.16 class T_remove_radar: total=1.20e+009, N=1, <>=1.20e+009, min=1.20e+009, max=1.20e+009 class T_main_loop_L1: total=1.89e+013, N=20, <>=9.44e+011, min=5.41e+011, max=1.13e+012 class T_FFT_forward: total=3.13e+011, N=291345, <>=1.07e+006, min=4.91e+005, max=1.09e+008 class T_remove_radar_randomize: total=6.82e+008, N=291345, <>=2.34e+003, min=8.81e+002, max=1.96e+006 class T_build_chirp_table: total=1.72e+010, N=155, <>=1.11e+008, min=1.04e+008, max=1.60e+008 class T_dechirp: total=2.58e+012, N=9323027, <>=2.77e+005, min=1.80e+001, max=1.61e+008 class T_FFT_inverse: total=8.49e+012, N=9323027, <>=9.10e+005, min=4.07e+005, max=1.62e+008 class T_ffa: total=4.28e+012, N=350, <>=1.22e+010, min=4.09e+009, max=7.73e+010 FFA blocks counters: class T_FFA_fetch: total=3.60e+012, N=21350570, <>=1.69e+005, min=3.93e+004, max=1.36e+008 class T_FFA_tt_build: total=0.00e+000, N=0, <>=0.00e+000, min=1.84e+019, max=0.00e+000 class T_FFA_compare: total=3.55e+011, N=905365320, <>=3.91e+002, min=1.80e+001, max=1.06e+008 class T_FFA_coadd: total=1.84e+011, N=905365320, <>=2.03e+002, min=1.80e+001, max=1.06e+008 class T_FFA_stride_add: total=1.87e+010, N=183248010, <>=1.01e+002, min=1.80e+001, max=5.32e+007 USE_INCREASED_PRECISION SMALL_CHIRP_TABLE BLANKIT TWINDECHIRP USE_LRINT rev 2692 00:16:05 (1720): called boinc_finish(0) </stderr_txt> ]]> 2nd result (stock CPU app, so no result shown): Task 5503955183 Name ap_19no09ab_B0_P0_00281_20170210_21323.wu_1 Workunit 2429434010 Created 11 Feb 2017, 5:00:43 UTC Sent 11 Feb 2017, 5:00:45 UTC Report deadline 8 Mar 2017, 5:00:45 UTC Received 8 Mar 2017, 8:23:04 UTC Server state Over Outcome Success Client state Done Exit status 0 (0x00000000) Computer ID 7468551 Run time 1 days 20 hours 30 min 43 sec CPU time 22 hours 31 min 27 sec Validate state Valid Credit 574.94 Device peak FLOPS 3.54 GFLOPS Application version AstroPulse v7 v7.00 x86_64-pc-linux-gnu Stderr output <core_client_version>7.2.42</core_client_version> <![CDATA[ <stderr_txt> In ap_gfx_main.cpp: in ap_graphics_init(): Starting client. Counts single:rep. 0:0 Starting large chunk at dm 896 Counts single:rep. 0:0 Starting large chunk at dm 1024 Counts single:rep. 0:0 Starting large chunk at dm 1152 Counts single:rep. 0:0 Starting large chunk at dm 1280 Counts single:rep. 0:0 Starting large chunk at dm 1408 Counts single:rep. 0:0 Starting large chunk at dm 1536 Counts single:rep. 0:0 Starting large chunk at dm 1664 Counts single:rep. 0:0 Starting large chunk at dm 1792 Counts single:rep. 0:0 Starting large chunk at dm 1920 Counts single:rep. 0:0 Starting large chunk at dm 2048 Counts single:rep. 0:0 Starting large chunk at dm 2176 Counts single:rep. 0:0 Starting large chunk at dm 2304 Counts single:rep. 0:0 Starting large chunk at dm 2432 Counts single:rep. 0:0 Starting large chunk at dm 2560 Counts single:rep. 0:0 Starting large chunk at dm 2688 Counts single:rep. 0:0 Starting large chunk at dm 2816 Counts single:rep. 0:0 Starting large chunk at dm 2944 Counts single:rep. 0:0 Starting large chunk at dm 3072 Counts single:rep. 0:0 Starting large chunk at dm 3200 Counts single:rep. 0:0 Starting large chunk at dm 3328 Counts single:rep. 0:0 Starting large chunk at dm 3456 In ap_gfx_main.cpp: in ap_graphics_init(): Starting client. Counts single:rep. 0:0 Starting large chunk at dm 3456 In ap_gfx_main.cpp: in ap_graphics_init(): Starting client. Counts single:rep. 0:0 Starting large chunk at dm 3456 Counts single:rep. 0:0 Starting large chunk at dm 3584 Counts single:rep. 0:0 Starting large chunk at dm 3712 Counts single:rep. 0:0 Starting large chunk at dm 3840 Counts single:rep. 0:0 Starting large chunk at dm 3968 Counts single:rep. 0:0 Starting large chunk at dm 4096 Counts single:rep. 0:0 Starting large chunk at dm 4224 Counts single:rep. 0:0 Starting large chunk at dm 4352 Counts single:rep. 0:0 Starting large chunk at dm 4480 Counts single:rep. 0:0 Starting large chunk at dm 4608 Counts single:rep. 0:0 Starting large chunk at dm 4736 Counts single:rep. 0:0 Starting large chunk at dm 4864 Counts single:rep. 0:0 Starting large chunk at dm 4992 Counts single:rep. 0:0 Starting large chunk at dm 5120 Counts single:rep. 0:0 Starting large chunk at dm 5248 Counts single:rep. 0:0 Starting large chunk at dm 5376 Counts single:rep. 0:0 Starting large chunk at dm 5504 Counts single:rep. 0:0 Starting large chunk at dm 5632 Counts single:rep. 0:0 Starting large chunk at dm 5760 Counts single:rep. 0:0 Starting large chunk at dm 5888 Counts single:rep. 0:0 Starting large chunk at dm 6016 Counts single:rep. 0:0 Starting large chunk at dm 6144 Counts single:rep. 0:0 Starting large chunk at dm 6272 Counts single:rep. 0:0 Starting large chunk at dm 6400 Counts single:rep. 0:0 Starting large chunk at dm 6528 Counts single:rep. 0:0 Starting large chunk at dm 6656 Counts single:rep. 0:0 Starting large chunk at dm 6784 Counts single:rep. 0:0 Starting large chunk at dm 6912 Counts single:rep. 0:0 Starting large chunk at dm 7040 Counts single:rep. 0:0 Starting large chunk at dm 7168 Counts single:rep. 0:0 Starting large chunk at dm 7296 Counts single:rep. 0:0 Starting large chunk at dm 7424 Counts single:rep. 0:0 Starting large chunk at dm 7552 Counts single:rep. 0:0 Starting large chunk at dm 7680 Counts single:rep. 0:0 Starting large chunk at dm 7808 Counts single:rep. 0:0 Starting large chunk at dm 7936 Counts single:rep. 0:0 Starting large chunk at dm 8064 Counts single:rep. 0:0 Starting large chunk at dm 8192 Counts single:rep. 0:0 Starting large chunk at dm 8320 In ap_gfx_main.cpp: in ap_graphics_init(): Starting client. Counts single:rep. 0:0 Starting large chunk at dm 8320 Counts single:rep. 0:0 Starting large chunk at dm 8448 Counts single:rep. 0:0 Starting large chunk at dm 8576 Counts single:rep. 0:0 Starting large chunk at dm 8704 Counts single:rep. 0:0 Starting large chunk at dm 8832 Counts single:rep. 0:0 Starting large chunk at dm 8960 Counts single:rep. 0:0 Starting large chunk at dm 9088 Counts single:rep. 0:0 Starting large chunk at dm 9216 Counts single:rep. 0:0 Starting large chunk at dm 9344 Counts single:rep. 0:0 Starting large chunk at dm 9472 In ap_gfx_main.cpp: in ap_graphics_init(): Starting client. Counts single:rep. 0:0 Starting large chunk at dm 9472 Counts single:rep. 0:0 Starting large chunk at dm 9600 Counts single:rep. 0:0 Starting large chunk at dm 9728 Counts single:rep. 0:0 Starting large chunk at dm 9856 Counts single:rep. 0:0 Starting large chunk at dm 9984 Counts single:rep. 0:0 Starting large chunk at dm 10112 Counts single:rep. 0:0 Starting large chunk at dm 10240 Counts single:rep. 0:0 Starting large chunk at dm 10368 Counts single:rep. 0:0 Starting large chunk at dm 10496 In ap_gfx_main.cpp: in ap_graphics_init(): Starting client. Counts single:rep. 0:0 Starting large chunk at dm 10496 Counts single:rep. 0:0 Starting large chunk at dm 10624 Counts single:rep. 0:0 Starting large chunk at dm 10752 Counts single:rep. 0:0 Starting large chunk at dm 10880 Counts single:rep. 0:0 Starting large chunk at dm 11008 Counts single:rep. 0:0 Starting large chunk at dm 11136 Counts single:rep. 0:0 Starting large chunk at dm 11264 Counts single:rep. 0:0 Starting large chunk at dm 11392 Counts single:rep. 0:0 Starting large chunk at dm 11520 Counts single:rep. 0:0 Starting large chunk at dm 11648 Counts single:rep. 0:0 Starting large chunk at dm 11776 Counts single:rep. 0:0 Starting large chunk at dm 11904 Counts single:rep. 0:0 Starting large chunk at dm 12032 Counts single:rep. 0:0 Starting large chunk at dm 12160 Counts single:rep. 0:0 Starting large chunk at dm 12288 Counts single:rep. 0:0 Starting large chunk at dm 12416 Counts single:rep. 0:0 Starting large chunk at dm 12544 Counts single:rep. 0:0 Starting large chunk at dm 12672 Counts single:rep. 0:0 Starting large chunk at dm 12800 Counts single:rep. 0:0 Starting large chunk at dm 12928 Counts single:rep. 0:0 Starting large chunk at dm 13056 Counts single:rep. 0:0 Starting large chunk at dm 13184 Counts single:rep. 0:0 Starting large chunk at dm 13312 Counts single:rep. 0:0 Starting large chunk at dm 13440 Counts single:rep. 0:0 Starting large chunk at dm 13568 Counts single:rep. 0:0 Starting large chunk at dm 13696 Counts single:rep. 0:0 Starting large chunk at dm 13824 Counts single:rep. 0:0 Starting large chunk at dm 13952 Counts single:rep. 0:0 Starting large chunk at dm 14080 In ap_gfx_main.cpp: in ap_graphics_init(): Starting client. Counts single:rep. 0:0 Starting large chunk at dm 14080 Counts single:rep. 0:0 Starting large chunk at dm 14208 Counts single:rep. 0:0 Starting large chunk at dm 14336 Counts single:rep. 0:0 Starting large chunk at dm 14464 In ap_gfx_main.cpp: in ap_graphics_init(): Starting client. Counts single:rep. 0:0 Starting large chunk at dm 14464 Counts single:rep. 0:0 Starting large chunk at dm 14592 Counts single:rep. 0:0 Starting large chunk at dm 14720 Counts single:rep. 0:0 Starting large chunk at dm 14848 Counts single:rep. 0:0 Starting large chunk at dm 14976 11:22:46 (2085): called boinc_finish(0) </stderr_txt> ]]> 3rd result (my): Task 5567860620 Name ap_19no09ab_B0_P0_00281_20170210_21323.wu_2 Workunit 2429434010 Created 8 Mar 2017, 5:00:46 UTC Sent 8 Mar 2017, 5:00:48 UTC Report deadline 2 Apr 2017, 5:00:48 UTC Received 8 Mar 2017, 11:03:29 UTC Server state Over Outcome Success Client state Done Exit status 0 (0x00000000) Computer ID 8221594 Run time 9 min 24 sec CPU time 2 min 48 sec Validate state Invalid Credit 0.00 Device peak FLOPS 8,601.60 GFLOPS Application version AstroPulse v7 Anonymous platform (ATI GPU) Peak working set size 102.40 MB Peak swap size 98.18 MB Peak disk usage 0.04 MB Stderr output <core_client_version>7.6.33</core_client_version> <![CDATA[ <stderr_txt> Running on device number: 3 Verbose level set to:0 DATA_CHUNK_UNROLL set to:18 FFA thread block override value:2830 FFA thread fetchblock override value:2830 TUNE: kernel 1 now has workgroup size of (64,4,1) TUNE: kernel 2 now has workgroup size of (64,4,1) oclFFT plan class overrides requested: global radix 256; local radix 16; max workgroup size 256 Priority of worker thread raised successfully Priority of process adjusted successfully, high priority class used OpenCL platform detected: Advanced Micro Devices, Inc. BOINC assigns device 3 Info: BOINC provided OpenCL device ID used Used GPU device parameters are: Number of compute units: 64 Single buffer allocation size: 256MB Total device global memory: 3072MB max WG size: 256 local mem type: Real Build features: Non-graphics BLANKIT OpenCL TWIN_FFA OCL_ZERO_COPY COMBINED_DECHIRP_KERNEL FFTW USE_INCREASED_PRECISION USE_SSE2 x86 CPUID: Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz Cache: L1=64K L2=256K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX AstroPulse v7 Windows x86 rev 2742, V7 match, by Raistmer with support of Lunatics.kwsn.net team. SSE2 OpenCL version by Raistmer oclFFT fix for ATI GPUs by Urs Echternacht ffa threshold mods by Joe Segur SSE3 dechirping by JDWhale Combined dechirp kernel by Frizz Number of OpenCL platforms: 1 OpenCL Platform Name: AMD Accelerated Parallel Processing Number of devices: 4 Max compute units: 64 Max work group size: 256 Max clock frequency: 1050Mhz Max memory allocation: 3018693957 Name: Fiji Vendor: Advanced Micro Devices, Inc. Driver version: 1912.5 (VM) Version: OpenCL 2.0 AMD-APP (1912.5) Max compute units: 64 Max work group size: 256 Max clock frequency: 1050Mhz Max memory allocation: 3018693957 Name: Fiji Vendor: Advanced Micro Devices, Inc. Driver version: 1912.5 (VM) Version: OpenCL 2.0 AMD-APP (1912.5) Max compute units: 64 Max work group size: 256 Max clock frequency: 1050Mhz Max memory allocation: 3018693957 Name: Fiji Vendor: Advanced Micro Devices, Inc. Driver version: 1912.5 (VM) Version: OpenCL 2.0 AMD-APP (1912.5) Max compute units: 64 Max work group size: 256 Max clock frequency: 1050Mhz Max memory allocation: 3018693957 Name: Fiji Vendor: Advanced Micro Devices, Inc. Driver version: 1912.5 (VM) Version: OpenCL 2.0 AMD-APP (1912.5) state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 single pulses: 0 repetitive pulses: 0 percent blanked: 8.30 TWIN_FFA OCL_ZERO_COPY USE_OPENCL OPENCL_WRITE USE_INCREASED_PRECISION SMALL_CHIRP_TABLE COMBINED_DECHIRP_KERNEL BLANKIT rev 2742 GPU device sync requested... ...GPU device synched 12:00:25 (2304): called boinc_finish(0) </stderr_txt> ]]> 1st result: single pulses: 0 repetitive pulses: 0 percent blanked: 8.16 3rd result (my): single pulses: 0 repetitive pulses: 0 percent blanked: 8.30 I don't think that the result is not the same. ;-) The small difference because '% blanked' is 'normal'. My/this PC is running with this setup since 1 1/2 years (October '15) and never got invalid AP results with (up to the latest 'stable' version) Crimson 15.12 (1912.5 driver in it). ID: 1854043 ·

Stephen "Heretic" Volunteer tester Send message Joined: 20 Sep 12 Posts: 5557 Credit: 192,787,363 RAC: 628	Message 1855282 - Posted: 13 Mar 2017, 14:12:52 UTC - in response to Message 1854032. Last modified: 13 Mar 2017, 14:15:34 UTC This is a "feature" - if the second party is late in returning, but does so before the third party they do get included in the validation process (I think there is a time limit on how late they can be - this is to allow for computers that only contact the servers at infrequent intervals rather than continuously.) Your result was returned after the validator had done its run between the first two, thus your result was "late" - the second party returned about three hours before you did. Without looking carefully at the outputs it is hard to see if your result was "significantly different" to the other two results, which might explain why the result was declared "invalid". . . Yep I was caught by that once or twice. A bummer dude! And I am pretty sure it is because the late result by the primary distribution host beat the result of the secondary recipient in time, in my case by minutes not hours. Stephen :( ID: 1855282 ·

petri33 Volunteer tester Send message Joined: 6 Jun 02 Posts: 1668 Credit: 623,086,772 RAC: 156	Message 1855309 - Posted: 13 Mar 2017, 16:30:44 UTC - in response to Message 1855282. This is a "feature" - if the second party is late in returning, but does so before the third party they do get included in the validation process (I think there is a time limit on how late they can be - this is to allow for computers that only contact the servers at infrequent intervals rather than continuously.) Your result was returned after the validator had done its run between the first two, thus your result was "late" - the second party returned about three hours before you did. Without looking carefully at the outputs it is hard to see if your result was "significantly different" to the other two results, which might explain why the result was declared "invalid". . . Yep I was caught by that once or twice. A bummer dude! And I am pretty sure it is because the late result by the primary distribution host beat the result of the secondary recipient in time, in my case by minutes not hours. Stephen :( You re right about the minutes. Here is a task run by your computer and a 1080. (No validation problems here) https://setiathome.berkeley.edu/workunit.php?wuid=2466647432 To overcome Heisenbergs: "You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones ID: 1855309 ·

Cosmic_Ocean Send message Joined: 23 Dec 00 Posts: 3027 Credit: 13,516,867 RAC: 13	Message 1855317 - Posted: 13 Mar 2017, 17:26:46 UTC That seems like a new "feature" to me to mark it as invalid, if it was indeed a valid result. It used to be that it was just in permanent limbo of "waiting to validate" and never would. I would venture a guess that maybe your result actually was invalid. I had also never seen that happen with AP--it always seemed to only affect MB. I had seen the timeline happen with AP, but all three would end up validating properly. Linux laptop: record uptime: 1511d 20h 19m (ended due to the power brick giving-up) ID: 1855317 ·

betreger Send message Joined: 29 Jun 99 Posts: 11361 Credit: 29,581,041 RAC: 66	Message 1855318 - Posted: 13 Mar 2017, 17:37:50 UTC - in response to Message 1855317. That seems like a new "feature" to me to mark it as invalid, if it was indeed a valid result. It used to be that it was just in permanent limbo of "waiting to validate" and never would. IIRC yes they used to get stuck, I haven't seen that in a long time. ID: 1855318 ·

©2024 University of California

SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.