Haven't anyone noticed all the "Validate Error" Status on what I can see all computers here on Beta, the last couple of days?
There's thousands of "validate error*", with all kind of apps, including CPU apps.

Since it's on what I can judge all computers, it has to be something wrong with Beta itself.

Edit: Why run Beta, if one doesn't keep an eye on what the computer is producing?

Haven't anyone noticed all the "Validate Error" Status on what I can see all computers here on Beta, the last couple of days?
There's thousands of "validate error*", with all kind of apps, including CPU apps.

Since it's on what I can judge all computers, it has to be something wrong with Beta itself.

Edit: Why run Beta, if one doesn't keep an eye on what the computer is producing?

You run BETA to test the application, so all those validate errors don't happen on MAIN!

Obviously someone is debugging the BETA code and will update it at some point. Perhaps until then the answer is to have no tasks to send.

Now if you want to help with code development, ... .

Haven't anyone noticed all the "Validate Error" Status on what I can see all computers here on Beta, the last couple of days?
There's thousands of "validate error*", with all kind of apps, including CPU apps.

Since it's on what I can judge all computers, it has to be something wrong with Beta itself.

Edit: Why run Beta, if one doesn't keep an eye on what the computer is producing?

You run BETA to test the application, so all those validate errors don't happen on MAIN!

Obviously someone is debugging the BETA code and will update it at some point. Perhaps until then the answer is to have no tasks to send.

Now if you want to help with code development, ... .

And the meaning of this reply of yours was what?
That I shouldn't point out when something "new" happens on Beta?
Of course I know it doesn't happen on main, that's why I didn't post it on main.
(strange reply to my simple "error" reporting.)

Duh........

The Task result pages often take so long to load I give up the will before I get the chance to check them. Having just waited patiently though I can confirm that I have loads of Invalid tasks too; over 100, most of which are since 14 December.

There has been discussion at main over a new app deployed here. May not apply to you, or maybe all your invalids are wingman running that app.

That being said, is it you or the wingman? Take a look at your invalids, it is one particular version that is failing validate? Theirs or yours? That is information to help.

Finally we could have run into some kind of splitter issue or a bad data tape. Can't say until we know it isn't one particular app version.

All the WU's that were completed but not uploaded over the Christmas break are now invalid. Not fair.

---

Space, the final frontier.
For us at least. If this thing works, then we might be eaten, or get a chance to roam the universe.

There was an issue with the validators before Christmas, from your comments it sounds as if it is still dragging on.

I have 81 validate errors that occurred on tasks issued in Dec between the 15th and 19th and returned either on the 20th or on the 9th Jan after the servers came back up.
Workunits like this one, https://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=12296196, all tasks returned in Dec invalid, re-issues in Jan Validated.

How do you get a Validate Error when the validation sequence hasn't been completed.
https://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=12307873

The host owner is Owensse, my result is "Completed, validation inconclusive", awaiting two more hosts to report.

I know I have a pile of finished tasks to return, I'm just not able to access the computer they are on just. now. Hopefully tomorrow they will be heading back to the servers.