Hi everyone,

I appreciate your patience while we worked through this.

v1.05 addresses the extreme runtime issues we've been facing lately.

I would recommend cancelling any v1.04 tasks that are running too long.

I'm looking into ways we can credit those who attempted to run broken v1.04 tasks, but as far as I can tell, boinc does not support that scenario. So I don't have an answer quite yet.

I'm deploying some more tasks worth 10,000 credits each as a consolation for this.

Please let me know if you run into any issues.

Thanks boysanic for the fix.
I however will keep running the tasks I am currently running (v1.04) simply because of the amount of hours I have already put into some of them.
My longest at the moment is 4 days 4 hours with another 12 hours to go.
This is followed by a 3 day 15 hour with another 2 days still to go.
A few others are well past 30 hours.

Conan

@boysanic didn't indicate that any task returned after deadline would get credit AFAIK. So no point in continuing to run the work after deadline in my opinion.

Tasks are giving 5000 points and complete at a normal time now.

BOINC will give credit to tasks that are returned and reported after the deadline as long as someone didn't return the resend back first.

Just to clarify, the existing task pool prior to what I generated this afternoon still has 5000 credits. The new batch has 10,000.

I might retroactively update the outstanding 5000 credit tasks to 10,000 but I had limited time today

Okay, that might be what I am seeing. The tasks I've completed that have validated appear to have started as 1.04, but timed out/was aborted and resent as 1.05.

There is a problem with Xoroshigo2 v1.05 - Runtime fix. Norton dedects all WUs as Troyan:

Nombre de la amenaza: Win64:Evo-gen [Trj]
Tipo de amenaza: Troyano - Esta amenaza simula ser otra cosa (p. ej., una imagen, un documento u otro archivo) para engañarte, de modo que lo ejecutes e infecte tu equipo.
Estado: Se movió a Cuarentena
Opciones: Informar de una falsa detección
Detectado por: Auto-Protect
En el equipo de: 19/4/25 10:42
Último uso: 19/4/25 10:42
Elemento de inicio: No

Version v1.04 did run without any problems after I made an exemption for the "xoroshigo2_wrapper_1.04_windows_x86_64" file.
The same I made with "xoroshigo2_wrapper_1.05_windows_x86_64" however each time a WU starts it creates a tmp file, something like "cpyB38D.tmp" each time with another name. This tmp file is put to quarantine.

You just need to set an exception for the entire BOINC directory to not be checked by your antivirus.

Hi everyone,

I appreciate your patience while we worked through this.

v1.05 addresses the extreme runtime issues we've been facing lately.

I would recommend cancelling any v1.04 tasks that are running too long.

I'm looking into ways we can credit those who attempted to run broken v1.04 tasks, but as far as I can tell, boinc does not support that scenario. So I don't have an answer quite yet.

I'm deploying some more tasks worth 10,000 credits each as a consolation for this.

Please let me know if you run into any issues.

Well... The one thing I'm finding lately, I'm not able to get ANY work done! Now, I'm running Linux, and I'm 'almost' certain that I've had work before.

---

Are you sure the following is met:

1. You're attached to the project.
2. BOINC isn't suspended.
3. No new work is not set.
4.You've selected the correct apps for your host. (CPU or GPU or Both)
5.The host isn't on a different venue that isn't configured correctly.


Additionally, what does the boinc log say when your host requests work?