"Update" overrides "No new tasks"?
25 Jun 2010 12:47:59 UTC
Topic 195185
(moderation:
While doing some troubleshooting on a Mac mini running OS X 10.4.11 with BOINC 6.10.56, I had set Einstein to send "No new tasks" for a while. However, when I finished a few tasks and they had uploaded but not yet reported I decided to hit the "Update" button to get them sent in and out of the way. At that point I began to get a new set of work units downloading. Is that the way "No new tasks" is supposed to work?
Thank you for any information anyone can supply.
Plus SETI Classic = 21,082 WUs
"Update" overrides "No new tasks"?
)
That must be a new "feature". In my (admittedly very) old BOINC, NNT definitely "survives" an update request.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
As it does in my new 6.10.57
)
As it does in my new 6.10.57 (64bit).
So, paris, in the Messages it shows when you set No new tasks. Can you find that anywhere in the messages? It'll show like this:
25/06/2010 16:41:55 Einstein@Home work fetch suspended by user
And furthermore, are you sure the tasks were downloaded? Not that they were already downloaded, but just not visible? BOINC 6.10 has a new button in the GUI, in the Tasks tab. It switches between "Show all tasks" and "Show active tasks". It starts default on Show active tasks, where active tasks are only those that are running, waiting to run and suspended. All tasks waiting to start and ready to report are not visible.
RE: As it does in my new
)
Strangely, even though I did not find the "work suspended" message (but the Projects tab showed that Einstein was set for NNT) I did find a "work fetch resumed" message after I clicked the "Allow new tasks" button. The tasks tab button is set for Showing all tasks ( (it reads "show active tasks" now). I did find some messages saying that "lost tasks" were being resent. That may have been the problem. I watched the downloads take place so I know that they were not hidden.
I had reset the project as part of the troubleshooting I was doing and it may have needed to renew the old tasks by downloading them again. It seems a strange way of proceeding but it makes a kind of sense, I suppose. The mystery may be solved. Thank you.
Plus SETI Classic = 21,082 WUs
When the server assigned
)
When the server assigned tasks to a client and they have not (yet) been reported as finished nor are communicated by the client as 'in progress' during scheduler contact, the scheduler sends these to the client again. I'd guess that this is independent of a work request ("requesting 0 seconds of work") as these are not new tasks as seen by the scheduler. Could it be that your client already got these tasks earlier, but threw them away (project reset etc)?
BM
BM
RE: Could it be that your
)
As paris said, (s)he had reset the project, which does throw away the work and binaries.
I wonder if that behaviour should change in the client. Of course, technically it's not new work, but you usually set the flag to disable BOINC from downloading any work while still being able to upload & report.
RE: I wonder if that
)
Well, look at that. If you don't ask, you get nothing. I asked and got [trac]changeset:21823[/trac]. :-)