Getting mostly errors from work recivede today

<core_client_version>8.0.2</core_client_version>
<![CDATA[
<message>
Den angivne fil blev ikke fundet.
 (0x2) - exit code 2 (0x2)</message>
<stderr_txt>

Error: Number of lc points is greater than MAX_LC_POINTS = 2000

</stderr_txt>
]]>

Yes, all the work units are incompatible with the existing applications. Need new applications with no hard-coded limits.

Georgi, acknowledged his mistake in keeping hard coded limits the last time we exceeded the lc datapoints.

Either they just delete all the new work and wait for new applications before generating more or just let the work get released until the WU's hit the failed threshold and are retired.

---

A proud member of the OFA (Old Farts Association)

Just snagged a couple, myself. This is through the Android app release May 8 2024 (and Boinc 8.0.4, though that doesn't really apply, I think). Downloaded some more WUs about two minutes later, and the next set started crunching; maybe a differently generated batch?

---

Within seconds of starting, eight of nine Asteroids tasks on my computer were marked computer errors.

One is currently running normally.

S. Gaber
Oldsmar, FL

All of the 'bad' incompatible WU's have been removed from distribution today. Shouldn't be getting any more errors.

---

A proud member of the OFA (Old Farts Association)

Except it looks like ALL of my tasks have now errored out with exceeded 'lc_points' for some reason.

---

A proud member of the OFA (Old Farts Association)

So that happened with all tasks from yesterday. Is there a way to inform about the problem or reset them to go through with it?

They know about the issue. Just that for some reason the admins never got around to releasing the new application to the general population as a standard application. You can build the app from the codebase and deploy it via the anonymous platform to be able to run the tasks that have the LC points > 2000 and have the task complete successfully.

---

A proud member of the OFA (Old Farts Association)

Still happening, 8 days later. That's really poor form.

<core_client_version>8.1.0</core_client_version>
<![CDATA[
<message>
process exited with code 2 (0x2, -254)</message>
<stderr_txt>

Error: Number of lc points is greater than POINTS_MAX = 2000

</stderr_txt>
]]>

Yes, it is very wasteful of our resources. Even with my ability to run the correct app, I more than likely will waste my computation on the task since it is unlikely I get a wingman who is running the correct app version to have my tasks validated. I waste normally half a dozen to a dozen or more tasks a day that end up erroring out after 7 other wingmen fail to run the task correctly.

---

A proud member of the OFA (Old Farts Association)

Still happening, 8 days later. That's really poor form.

<core_client_version>8.1.0</core_client_version>
<![CDATA[
<message>
process exited with code 2 (0x2, -254)</message>
<stderr_txt>

Error: Number of lc points is greater than POINTS_MAX = 2000

</stderr_txt>
]]>

resends can take months to fizzle out

---

Yes, it is very wasteful of our resources. Even with my ability to run the correct app, I more than likely will waste my computation on the task since it is unlikely I get a wingman who is running the correct app version to have my tasks validated. I waste normally half a dozen to a dozen or more tasks a day that end up erroring out after 7 other wingmen fail to run the task correctly.

it's really only wasteful for the few folks who have a working application for the tasks with lc_points too high. everyone else the tasks fail almost instantly and waste no time. i think i've had more success than invalids from the batch and there have been a few instances where i got lucky to be paired (eventually) with another host with the good app and validating. at least a few of them are making it through the gauntlet

---