Hi everyone,
when I set WUProp@home to stop receiving new tasks through BOINC Manager, it doesn't work.
It continuously gets a new task as soon as I cancel the current one and update the project.
I tested it in two different computers:
- Ubuntu Linux, 3.13.0-44-generic, 32 bits, BOINC 7.2.42
- Windows 7, 64 bits, BOINC 7.4.27

What I do is:
1. set no new tasks.
2. cancel the current task in progres.
3. update the project.
and then I inmediately get a new task, no matter how many times and different ways I try.

Is this the default behavior for non-CPU-intensive projects or is it a bug?

Thanks,
Yacob

Actually, my bad, let me reformulate it:
I tried in 4 computers: it happens in the 2 Linux computers that I tried (both Ubuntu Linux, 3.13.0, 32 bits, BOINC 7.2.42), but it works in 2 Windows 7 computers (one 32 and one 64 bits).

Hi everyone,
when I set WUProp@home to stop receiving new tasks through BOINC Manager, it doesn't work.
It continuously gets a new task as soon as I cancel the current one and update the project.
I tested it in two different computers:
- Ubuntu Linux, 3.13.0-44-generic, 32 bits, BOINC 7.2.42
- Windows 7, 64 bits, BOINC 7.4.27

What I do is:
1. set no new tasks.
2. cancel the current task in progres.
3. update the project.
and then I inmediately get a new task, no matter how many times and different ways I try.

How did you 'cancel' the task in progress?, there is no 'cancel' button, you may eithier 'Abort' a workunit, or 'Reset' the project,

What does the Event Log say? Does Boinc ask for work? If Boinc doesn't ask for work, the Scheduler shouldn't send it.
the exception is projects with older Boinc server software, where 'resend lost tasks' still happens even with NNT set,
If you reset the project that task is still allocated to your host, The project may or not resend it depending whether 'resend lost tasks' is enabled,
and how new or old it's scheduler is.

Claggy

I "cancel" the task by clicking in the Abort button, I didn't reset the project at all.
Sorry for the confusion.

The log says as follows:

1. set no new tasks:

Mon 26 Jan 2015 07:11:17 PM EST | WUProp@Home | work fetch suspended by user

2. abort the current task:

Mon 26 Jan 2015 07:11:47 PM EST | WUProp@Home | task wu_v4_1422115582_41640_0 aborted by user

Mon 26 Jan 2015 07:11:48 PM EST | WUProp@Home | Computation for task wu_v4_1422115582_41640_0 finished

3. update the project:

Mon 26 Jan 2015 07:12:32 PM EST | WUProp@Home | update requested by user

Mon 26 Jan 2015 07:12:33 PM EST | WUProp@Home | Sending scheduler request: Requested by user.

Mon 26 Jan 2015 07:12:33 PM EST | WUProp@Home | Reporting 1 completed tasks

Mon 26 Jan 2015 07:12:33 PM EST | WUProp@Home | Not requesting tasks: non CPU intensive

Mon 26 Jan 2015 07:12:39 PM EST | WUProp@Home | Scheduler request completed

and then I inmediately get a new task.
No other message logs are displayed until BOINC naturally resumes work by computer inactivity.

I don't know if BOINC asks for work just by reading the output of the log. Maybe you can tell me.

Mon 26 Jan 2015 07:12:33 PM EST | WUProp@Home | Not requesting tasks: non CPU intensive

I don't know if BOINC asks for work just by reading the output of the log. Maybe you can tell me.

Now I know what to look for, here's a changeset that probably applies:

scheduler: send NCI jobs even if no work request

scheduler: send NCI jobs even if no work request

Claggy

Excuse me, Claggy, but what does that mean? The "changeset"...?
What is a changeset?
Is it BOINC programmed to request NCI jobs even if I specify not to do it?
Or is it a bug?

Thanks for your help,
Yacob

Excuse me, Claggy, but what does that mean? The "changeset"...?
What is a changeset?

A Changeset is a Code change.

Is it BOINC programmed to request NCI jobs even if I specify not to do it?

No, It's the other way around, Boinc isn't requesting NCI work, But the server's scheduler ignores that Boinc isn't asking for work, and sends NCI work anyway.

NCI means non compute intensive, there is no CPU load, or if any, minimal CPU load,
why would you want to suspend a NCI project like WUProp@home or Radioactiveathome, If you have a sensor connected shouldn't you keep sending your sensor data?

Claggy

Thanks for the reply, Claggy.

why would you want to suspend a NCI project like WUProp@home or Radioactiveathome, If you have a sensor connected shouldn't you keep sending your sensor data?

First reason: I just want to suspend WUProp@home because I don't have any other project running at the moment in the computer. Most of the times is going to be off, so any task would pass deadline before completition.
And, as far as I understand, WUProp@home monitors behavior of WUs of other projects.
Therefore, if I don't have WU, any WUProp task is doing nothing there, just consuming CPU, no matter how little.

Second: If I say "no new tasks", why the project has to override my decision? It simply annoys me.
If that changeset is so good, why is only implemented in Linux but not Windows versions?

Anyway, you replied all my questions.
Thanks, Claggy!

Best,
Yacob

Hi,

I fixed the problem.

Sebastien
WUProp administrator

Tested and confirmed.

Thanks Sebastien!

Yacob