Joined: 18 Nov 08
Not sure if this is a bug or an "info" but I occasionally see the following;. It appears they only occur in the "testing" apps
43 Milkyway@Home 10/25/2019 6:01:05 PM Found finish file for de_modfit_14_bundle5_testing_4s3f_1_1570151403_10505344_1; exit code 0 44 Milkyway@Home 10/25/2019 6:01:05 PM Task de_modfit_14_bundle5_testing_4s3f_1_1570151403_10505344_1: no shared memory segment 45 Milkyway@Home 10/25/2019 6:01:05 PM Found finish file for de_modfit_14_bundle4_testing_3s4f_3_1570151403_10501248_1; exit code 0 46 Milkyway@Home 10/25/2019 6:01:05 PM Task de_modfit_14_bundle4_testing_3s4f_3_1570151403_10501248_1: no shared memory segment
I was unable to find the above tasks to see their status. Got too many to go through. I would think that "exit code 0" means no error, at least on the pc.
Joined: 24 Jan 11
I think that is info only and caused by the parameters supplied for the testing tasks. There is an actual shared memory segment access error too but that has to do with a malfunctioning card, application or client upset.
[Edit] You can cause the error easily if you have the leave tasks in memory toggled in Preferences. Whole bunch of stuff added in 2007 checkin_notes
©2020 Astroinformatics Group