The NBody simulation code completely ignores the BOINC preferences for network availability. When I suspend all network activity, the Milkyway app will still try to upload its result when finished. This needs to be fixed.

Should mention I'm using boinc 6.10.45 x86_64. All other projects that I'm attached to respect the network preferences.

The NBody simulation code completely ignores the BOINC preferences for network availability. When I suspend all network activity, the Milkyway app will still try to upload its result when finished. This needs to be fixed.

Should mention I'm using boinc 6.10.45 x86_64. All other projects that I'm attached to respect the network preferences.

This isn't something milkyway controls.

Maybe, but I can prove that BOINC does this. There is a bug somewhere, even if it's not in the milkyway code specifically.

20-Jan-2011 09:00:00 [---] Suspending network activity - time of day
20-Jan-2011 09:01:56 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 09:06:57 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 09:11:56 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 09:16:57 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 09:21:57 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 09:26:58 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 09:31:58 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 09:36:58 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 09:41:58 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 09:46:58 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 09:51:59 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 09:56:59 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 10:01:59 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 10:07:00 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 10:11:59 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 10:17:00 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 10:22:00 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 10:27:00 [Milkyway@home] [task_debug] result de_nbody_model6_4_8721_1295496950_0 checkpointed
20-Jan-2011 10:28:48 [Milkyway@home] [task_debug] Process for de_nbody_model6_4_8721_1295496950_0 exited
20-Jan-2011 10:28:48 [Milkyway@home] [task_debug] task_state=EXITED for de_nbody_model6_4_8721_1295496950_0 from handle_exited_app
20-Jan-2011 10:28:48 [Milkyway@home] [task_debug] exit status 0
20-Jan-2011 10:28:48 [Milkyway@home] [task_debug] result state=FILES_UPLOADING for de_nbody_model6_4_8721_1295496950_0 from CS::app_finished
20-Jan-2011 10:28:48 [Milkyway@home] [task_debug] result state=FILES_UPLOADED for de_nbody_model6_4_8721_1295496950_0 from CS::update_results

I think I figured out why I'm observing these messages. The milkyway@home applications do not generate a result file, but instead they put the result in the stderr section of the scheduler request (reporting as complete). There is no result file to upload.