Got 1 Beta and finished it in just over 5 hours.
For some reason although Boinc uploaded it (07:00 GMT - UK time) it did not report it or any other tasks? It uploaded at least one WCG task subsequent to that.
- Boinc Version 6.10.18, Win7 Pro 64bit
When I clicked on Update it did report it and the other tasks waiting to be uploaded.
- Internet is always connected.
The wingmen finished in 6.5 and 9h, and managed to report before me. I am awaiting validation (Edit - now Validated).
Changed the connect about every 0.01 days to 0.10 days, but the 0.01 days seems to work fine on my other systems.
- Q9400 CPU
- Drive has 100GB free. Boinc was set to use up to 20GB, and leave 5GB free, so no obvious issues there.
- 4GB RAM, using less than 1.7GB. I have now allowed up to 50GB, just in case.
I did suspend one WCG task so that the Beta would run, and forgot to enable it again. Perhaps that was an issue?
However, even when the system finished all other tasks, and had no work, it did not pick up any new WCG tasks;€“ it did not even ask for new WCG tasks. New Project tasks were allowed and no web changes have been made in last 24h.
The only other Boinc project on the systems is GPUGrid which did pick up new tasks.

Reported the first 2, now in PV, no wingmen in sight,

BETA_ erlc_ a049_ pe0000_ 1-- 95711 Pending Validation 1/15/10 23:02:09 1/16/10 14:41:04 14.03 150.3 / 0.0
BETA_ erlc_ a048_ pe0000_ 0-- 95711 Pending Validation 1/15/10 23:01:49 1/16/10 14:40:42 13.89 148.9 / 0.0

The last 2 BETA jobs I forced to start and then suspended them and resumed, now waiting to run to let 2 suspended rice jobs finish, and to simulate an interruption. If they succeed, another piece then is known to get properly identified during the validation [if bits of this activity gets included in the result log or the result files].

One might also use the logic that as YOU had suspended a task that you still had work and chose not to do it so did not need anymore as opposed to Aborting a task. Also if you suspend/resume to move a task up, if you should reboot or stop/restart the manager it will resume the oldest tasks first

You're addressing people at the wrong forum > go here http://boinc.berkeley.edu/dev/index.php, where they, the developers, don't listen either... they even advertise that, so they employ gophers [volunteers like me] to carry problems back and forth.

The task suspend > no work fetch has been around for as long as I can remember... at least since the additional buffer function was introduced. Why send you work if you suspended work in the first place? You made the choice! And, result files from other running tasks will still be uploaded.

But, I'd agree, that if a job is suspended, a status change should show in the project tab such as "work fetch suspended [indefinitely], because manual task holds are active" or something like that. And a task suspend could e.g. be followed with an additional line such as "until all project tasks are allowed to process work fetch is suspended" in the message log... but as it is BOINC was designed for techno hobbyists and not for the masses. I've posted that statement a few times at the developers forum, which I consider one of the root causes of the low retention (WCG is though quite a bit higher than any other project, due hard work.)

Anyway we have several threads in BOINC forum and Chat Room to plant ideas... here in a Beta test thread it's near guaranteed to get lost or forgotten.

PS: And I did not say communications was stopped or suspended. It's delayed, up to 24 hours, where a secondary counter even forces a server check in every 48 hours (was 72). If computing in general is suspended, then networking does get suspended. There's a good reasons for that, such as to facilitate backups and restores without effecting affecting server contact counters.

edit: Running backups whilst the core client is loaded is anyhow a bad idea, but a restore of such a backup might actually produce a stable resume point. Dicey.

Your second wingmen could get an instruction to return to base... abort mission, if the first 2 in the quorum hit target! All depends if the first rounds were fired or not :-]