Hear, Hear! You are so right. [rant on] This situation is near intolerable and should NEVER be allowed to occur. This "you can check Twitter" is not a solution either -- I refuse to delve into that cesspit and refuse to use any sort of anti-social media for such purposes (or any other purpose for that matter). If WCG has a message, our email addresses are on file so send us a heads-up Someone should be able to cook up and test a script to do this task in a day or less. This email should, of course, be in addition to something in that 'notices' tab which has seldom if ever been used to any good effect in my experience.[rant off]

Even if they make no special allowance we should get our credits because they are normally only marked as "No Reply" when they are overdue and a resend goes out. They don't become "Too Late" when 2 copies have been validated.

However, I would expect that they would not issue re-sends until after they have caught up with the Reporting.

Mike

Oh, that was just another attempt to post a motivational message for WCG Team. Don't want to blame anyone. I beleive that was a strategic fail by IBM (but not for IBM of course) and we just need to move on.

The inconsistency of current WCG iteration made me to search for other ways of having fun with crunching, especially when I constantly need to jump between projects. For this reason I have joined competitions like Formula BOINC and BOINC Games.

That's right, Mike.
I have got two tasks that are marked "No Reply" at the moment. Let's have a look at them:

$ wcgstats -wsN -a0 -m0 -S -S
* Let's try to locate the workunit.
Loading results ...
There is 1 page of results available.

* Showing page 1/1 of all tasks with status ’N’ on all of your devices:
 <1> * OPNG_0212196_00111_0  Fedora Linux  No Reply              2023-12-01T05:38:32  2023-12-04T05:38:32
 <1>   OPNG_0212196_00111_1                Waiting to be sent  

 <2> * OPNG_0212134_00251_0  Fedora Linux  No Reply              2023-12-01T04:33:11  2023-12-04T04:33:11
 <2>   OPNG_0212134_00251_1                Waiting to be sent  


- Did this show the desired workunit? [Y (yes)/n (no, next)/p (previous)/l (last)/q (quit)/c (change)/* (match)/PAGENUMBER] q

So, as soon as they are marked "No Reply", because they couldn't get validated when they passed their deadlines, a duplicate would get generated. Normally, the duplicate would get distributed, a client would pick it up.
Now, that last thing is some kind of a problem: there is no client to receive any task because that part of the system is stuck (remember the error "Another scheduler instance is running for this host"?).
So the tasks can't get validated because the distribution of tasks is stuck, and since the scheduling part of the system is broken, they can't get reported. Now, as soon as the scheduler is working again and the tasks are reported — they have already been uploaded (that part is working most of the time at present) — they will get validated and there would be no need to send the tasks that are "Waiting to be sent" to the wingmen.
Finally, even if some part of the tasks that are "Waiting to be sent" are distributed, the tasks that are reported by us can get validated then, even if they passed their deadlines. (Remember the fact that a task that missed its deadline can get promoted from No Reply to Pending Validation? Example here in post 686132.)

Adri

Can you imagine, that people have better things to spend their weekends on than their fu**ing job, on which they already spend the whole week? In particular if they are not getting payed for working on weekends (and I'm sure WCG staff isn't)? There is no urgency, this is not something anybody's life depends on!



Either that or set up backup projects, whatever is better suited to prevent such completely unnecessary outbursts of anger in the future. I suggest backup projects.