Message boards :
Number crunching :
Too quick to be true?
Message board moderation
Author | Message |
---|---|
Send message Joined: 10 Nov 07 Posts: 96 Credit: 29,931,027 RAC: 0 |
My G5 Mac computed one task, gs_10_1196130779_5743_1, in only 27 seconds; all the others it’s done have taken just under 3.5 minutes. The result claims to have completed successfully, although the output file says APP: error writing checkpoint (resolving checkpoint file) -108 output_path: astronomy_checkpoint The validation state is “Initialâ€, but it seems to have been granted two credits anyway. |
Send message Joined: 8 Oct 07 Posts: 289 Credit: 3,690,838 RAC: 0 |
My G5 Mac computed one task, gs_10_1196130779_5743_1, in only 27 seconds; all the others it’s done have taken just under 3.5 minutes. The result claims to have completed successfully, although the output file saysAPP: error writing checkpoint (resolving checkpoint file) -108 output_path: astronomy_checkpoint Is it possible that the result was paused at any point? That might explain the apparent erroneous time.Travis said the app starts the task looking for a cp so all work has this error message. |
Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0 |
My G5 Mac computed one task, gs_10_1196130779_5743_1, in only 27 seconds; all the others it’s done have taken just under 3.5 minutes. The result claims to have completed successfully, although the output file saysAPP: error writing checkpoint (resolving checkpoint file) -108 output_path: astronomy_checkpoint there were a couple workunits sent out with a smaller volume than they should have, so they run really quickly. there weren't too many made like this so they should all be out of the system shortly. The thing about the checkpoint file is just some extra output that we didn't take out of the binary -- nothing wrong there. |
©2025 Astroinformatics Group