WU's 18465 & 18466 exceed expiration on a Rasperry Pi

[ETA_2025]

WU's 18465 & 18466 are both exceeding the timeout, and either due to be completed just before the expiration, or after the expiration, on Raspberry Pi hardware.

It's only in the last few days that I started receiving these WU's.

[Joe_H]

These two projects just recently moved out of beta testing to being assigned to all folders. There was a request to block assignment to ARM that was put in place 4 days ago. If you are still getting them, respond here and we will ask them to recheck that restriction.

[ETA_2025]

I haven't had any assigned since Jan 30 @ 2130 UTC+11.

[ETA_2025]

Joe_H I've now had three more assigned, with the most recent assigned on Feb 2 @ 6:05Z. I having to dump them all, because they can't be completed before expiration.

[Joe_H]

I will pass that on and ask that the restriction be rechecked.

[ETA_2025]

I've got two more 18465 WU's, with the most recent assigned on Feb 4 @ 5:07Z

[ETA_2025]

I'm still getting (and dumping) 18465 and 18466 WU's, with the most recent assigned on Feb 9 @ 9:30Z

[ETA_2025]

This is beyond ridiculous.

My PC and Pi's are both getting 18465 & 18466 WU's, with the same 3½ day expiry, and the same base points, but the PC can complete the WU in 15 hours, while the Pi's need 4 days!

Also, my Pi's can't seem get anything but 18465 & 18466 WU's at the moment. I've now had to dump 9 in a row, on a single Pi!

I have no problem completing 18465 & 18466 WU's on my PI's, but the expiry needs to be doubled, so that they can be completed within the timeout.

[toTOW]

I'm hit too ...

Code: Select all

18:01:04:WU01:FS00:0xa8: CPU: Cortex-A
18:01:04:WU01:FS00:0xa8: CPU ID: Arm Family 8 Model 72 Stepping 3
18:01:04:WU01:FS00:0xa8: CPUs: 4
18:01:04:WU01:FS00:0xa8: Memory: 3.70GiB
18:01:04:WU01:FS00:0xa8:Free Memory: 589.52MiB
18:01:04:WU01:FS00:0xa8: Threads: POSIX_THREADS
18:01:04:WU01:FS00:0xa8: OS Version: 5.15
18:01:04:WU01:FS00:0xa8:Has Battery: false
18:01:04:WU01:FS00:0xa8: On Battery: false
18:01:04:WU01:FS00:0xa8: UTC Offset: 0
18:01:04:WU01:FS00:0xa8: PID: 1523428
18:01:04:WU01:FS00:0xa8: CWD: /var/lib/fahclient/work
18:01:04:WU01:FS00:0xa8:********************************************************************************
18:01:04:WU01:FS00:0xa8:Project: 18466 (Run 39, Clone 27, Gen 11)

[ETA_2025]

This is crazy!

My PC is doing an 18460 WU, with a 7-day Timeout, which it will complete in 21 hours. My Pi's continue to get both 18465 & 18466 WU's, with a 3½-day expiry, which I have to dump, because they can't complete processing the WU before it expires.

Please just extend the Timeout for the 18465 & 18466 WU's, to 7-days too, as folding was never meant to be a job. Now, I have to frequently check which project each of my 10 Pi's is doing, and inevitably dump the new WU, hopefully without having wasted too much time and power, before I do.

[ETA_2025]

Thankfully, it appears that the Pi's are no longer getting 18465 or 18466 WU's. The last time that I received one of these two WU's was 2½ days ago.

But, I'll say again, that increasing the Timeout would solve the problem. So, can different categories of hardware get different Timeouts for the same project?

[Joe_H]

So, can different categories of hardware get different Timeouts for the same project?

No

[ETA_2025]

So, can different categories of hardware get different Timeouts for the same project?

No

Thanks Joe.