Please post any problems with the new application on PPC OS X machines here.

---

Dont think the error is PPC related, but it happens on a G3-350 MHz iMac running Mac OS 10.3.9. App was Version 0.01.
BOINC was limitet to use only 128 MB RAM at this time, i upped it to 192 MB. Whats the limit of RAM-usage for this type of WUs?

####
Sat 22 Nov 12:09:08 2008|Milkyway@home|Starting task nm_test3_5_1227379417_0 using milkyway version 1
Sat 22 Nov 18:08:56 2008|Milkyway@home|Aborting task nm_test3_5_1227379417_0: exceeded memory limit 138.19MB > 128.03MB
Sat 22 Nov 18:08:57 2008|Milkyway@home|Computation for task nm_test3_5_1227379417_0 finished
Sat 22 Nov 18:08:57 2008|Milkyway@home|Output file nm_test3_5_1227379417_0_0 for task nm_test3_5_1227379417_0 absent

I have a Mac G3-300MHz OS X 10.3.9 and the new test app doesn't download. I changed preferences to allow it, quit BOINC, deleted the old app, restarted BOINC, and it downloaded the 1.22 app again.

C

---

Team MacNN

You have to enable test applications in your preferences. If you go to the "Your account" page on MilkyWay, click "Computing preferences", then "Edit preferences" near the bottom. Check the box for test applications, save them, then force an update to MW from BOINC. That'll download the new preferences and allow you the new applications.

Hmm, i changed only the settings to allow test-WUs and let Boinc request for work. First download was a test-WU.

Try to reset the project in the BOINC client, but this will delete all work you have received.
Maybe there are no test-WU ready to send at this time, i also get only work for 1.22


@Travis
Second test WU with app 0.01 does not surive a restart of the BOINC-Client - it quit a few seconds after restart with the "Outputfile absent" error.
Oddly no automatic download of app 0.02 happend, only the test5 WU was downloaded.

You have to enable test applications in your preferences. If you go to the "Your account" page on MilkyWay, click "Computing preferences", then "Edit preferences" near the bottom. Check the box for test applications, save them, then force an update to MW from BOINC. That'll download the new preferences and allow you the new applications.

As I said in my previous post, I changed preferences to allow test apps to run, then restarted BOINC. I just now did an update on MW, and it did nothing other than continue to crunch using v1.22 app.

C

---

Team MacNN

You have to enable test applications in your preferences. If you go to the "Your account" page on MilkyWay, click "Computing preferences", then "Edit preferences" near the bottom. Check the box for test applications, save them, then force an update to MW from BOINC. That'll download the new preferences and allow you the new applications.

As I said in my previous post, I changed preferences to allow test apps to run, then restarted BOINC. I just now did an update on MW, and it did nothing other than continue to crunch using v1.22 app.

C

I'm only putting out WUs in limited amounts right now -- so if there isn't a WU for the new app available on the server, i don't think you'll download the new app. I think they're getting snatched up pretty quickly.

---

Hmm, i changed only the settings to allow test-WUs and let Boinc request for work. First download was a test-WU.

Try to reset the project in the BOINC client, but this will delete all work you have received.
Maybe there are no test-WU ready to send at this time, i also get only work for 1.22


@Travis
Second test WU with app 0.01 does not surive a restart of the BOINC-Client - it quit a few seconds after restart with the "Outputfile absent" error.
Oddly no automatic download of app 0.02 happend, only the test5 WU was downloaded.

Looks like this might be a checkpointing problem. Did you have a WU for the new app running when you did the restart?

---

Hmm, i changed only the settings to allow test-WUs and let Boinc request for work. First download was a test-WU.

Try to reset the project in the BOINC client, but this will delete all work you have received.
Maybe there are no test-WU ready to send at this time, i also get only work for 1.22


@Travis
Second test WU with app 0.01 does not surive a restart of the BOINC-Client - it quit a few seconds after restart with the "Outputfile absent" error.
Oddly no automatic download of app 0.02 happend, only the test5 WU was downloaded.

Looks like this might be a checkpointing problem. Did you have a WU for the new app running when you did the restart?

Yes it was an test5 WU.

I just received my first Test-units. However, in the BOINC client it says "work unit aborted by project" but the WUs get deleted from the server so quickly that I did not have a chance to check the details in the work-unit ID.

---

I just received my first Test-units. However, in the BOINC client it says "work unit aborted by project" but the WUs get deleted from the server so quickly that I did not have a chance to check the details in the work-unit ID.

i deleted the nm_test23 WUs because they had a problem with files not being present. there should be a bunch of test24s available that should work.

---

O.k., first work-unit finished and validated after 1,355.74 seconds (appr. 22.5 minutes) on a G5 Dual 2.7GHz with MacOS X 10.4.11. Claimed credit is 6.57, granted credit is 9.97.
Task ID 55082109
Name nm_test24_210_1227638440_0
BOINC manager estimated 52 hours(!).

Task details:
stderr out

<core_client_version>6.2.18</core_client_version>
<![CDATA[
<stderr_txt>
APP: error reading checkpoint (opening file)
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
called boinc_finish

</stderr_txt>

---

Just finished another few, this time app version 0.04. They are a little shorter than the 0.02 units.

Still the same stderr out

<core_client_version>6.2.18</core_client_version>
<![CDATA[
<stderr_txt>
APP: error reading checkpoint (opening file)
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
called boinc_finish

</stderr_txt>
]]>

---

Just finished 3 wus with app.04, nm_test25_4350_1228009540_0, nm_test26_4722_1228009628_0 and nm_test27_5041_1228009684_0, on my G5 1.80GHz iMac running 10.3.9 (panther) All completed successfully in just over 21 minutes and validated. All show the same checkpoint error in the stderr out

APP: error reading checkpoint (opening file)
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
...and so on

Not really a problem, but an observation.
On my G3 app v0.10 was the fastest version (10 minutes less), v0.12 and v0.07 gives the roughly same times. All versions are granted with the same credits of 39.xx.
On my G4 v0.12 (8150 sec) are a little slower than v0.09 or v0.10 (ca 7900), but are allways granted with 41.xx gredits. v0.07 also gets 39.xx on this Mac.