I just checked all my hosts for invalids from Apr 5/6. Most invalids that remain (after the fix) are marked 'too late to validate' which is somewhat suspicious as the 'sent' timestamp is less than 24 before the reported time...
I just checked all my hosts for invalids from Apr 5/6. Most invalids that remain (after the fix) are marked 'too late to validate' which is somewhat suspicious as the 'sent' timestamp is less than 24 before the reported time...
Hmm, not for me. Only one of my tasks that was marked as "Validation Error", yesterday, ended up being "too late to validate", after this issue was resolved. But, I ended up with 8 invalid tasks for April 5/6. On average, I would expect just one invalid task each day, sometimes none--I check every day--so that is well above average. It looks like these WUs ended up being validated by a quorum of 2 other machines, and the 2 other results returned were marked as invalid.
So, it looks like there is some randomness is the similarity of results, and, therefore, chances of validation decrease as more comparisons are made. Hmm, this is ironic, because I've been reading about Familywise Error (FWE) rate, recently.
In any case, seems like things are getting back to normal, and this will be just be a blip. Even more recent, validated tasks show their WUs were only sent to two machines. That is more like what I'm used to seeing for validate tasks from before I noticed this issue. My only concern, as always, is detecting problems on my end as early as possible. Again, thanks to everyone for contributing your experiences, which helped me not freak out about this.
Well, these 'too late' tasks are an unexpected and unintended side-effect of the re-validation of quite some more tasks than what are required for a quorum. I'll fix that. Not sure if I can make these all 'valid', but at least I'll manually grant credit for these.
I manually granted credit for all these "too late" tasks of the charge. Unfortunately rolling back the "validate state" (consistently) isn't that easy, sorry if these "invalid" tasks mess up your personal statistic. These shouldn't stay in the DB for more than a week.
Well, these 'too late' tasks are an unexpected and unintended side-effect of the re-validation of quite some more tasks than what are required for a quorum. I'll fix that. Not sure if I can make these all 'valid', but at least I'll manually grant credit for these.
Oh, I saw they remain 'invalid' but credit is now granted anyway. Thanks for that.
I just checked all my hosts
)
I just checked all my hosts for invalids from Apr 5/6. Most invalids that remain (after the fix) are marked 'too late to validate' which is somewhat suspicious as the 'sent' timestamp is less than 24 before the reported time...
mountkidd wrote: I just
)
Hmm, not for me. Only one of my tasks that was marked as "Validation Error", yesterday, ended up being "too late to validate", after this issue was resolved. But, I ended up with 8 invalid tasks for April 5/6. On average, I would expect just one invalid task each day, sometimes none--I check every day--so that is well above average. It looks like these WUs ended up being validated by a quorum of 2 other machines, and the 2 other results returned were marked as invalid.
So, it looks like there is some randomness is the similarity of results, and, therefore, chances of validation decrease as more comparisons are made. Hmm, this is ironic, because I've been reading about Familywise Error (FWE) rate, recently.
In any case, seems like things are getting back to normal, and this will be just be a blip. Even more recent, validated tasks show their WUs were only sent to two machines. That is more like what I'm used to seeing for validate tasks from before I noticed this issue. My only concern, as always, is detecting problems on my end as early as possible. Again, thanks to everyone for contributing your experiences, which helped me not freak out about this.
Well, these 'too late' tasks
)
Well, these 'too late' tasks are an unexpected and unintended side-effect of the re-validation of quite some more tasks than what are required for a quorum. I'll fix that. Not sure if I can make these all 'valid', but at least I'll manually grant credit for these.
BM
I manually granted credit for
)
I manually granted credit for all these "too late" tasks of the charge. Unfortunately rolling back the "validate state" (consistently) isn't that easy, sorry if these "invalid" tasks mess up your personal statistic. These shouldn't stay in the DB for more than a week.
BM
Bernd Machenschalk
)
Oh, I saw they remain 'invalid' but credit is now granted anyway. Thanks for that.
Soli Deo Gloria