Project: 18258 (Run 93, Clone 5, Gen 14)

[Mactin]

Overnight (2025-10-24), I processed p18258-r93-c5-g14 on my GPU. I got 324406 points for it. No apparent problems.

However, the same WU was processed successfully by another donor last month (2025-09-30).
Checking the same string they where all processed in double down to Gen 0

p18258-r93-c5-g13 in double.
p18258-r93-c5-g12 in double.
p18258-r93-c5-g11 in double.
...
p18258-r93-c5-g2 in double.
p18258-r93-c5-g1 in double.
p18258-r93-c5-g0 in double.

looking past my results
p18258-r93-c5-g15 in double.
p18258-r93-c5-g16 as allready been folded on 2025-09-30,

I dont know if this anomaly repeats elswhere or if this normal behavior.

[muziqaz]

It probably is display bug on the client or server

[Mactin]

It probably is display bug on the client or server

What is a « display bug » ? I dont understand !

[muziqaz]

It means things are broken server/client side

[Joe_H]

In this case there is no display bug. There are two possibilities here. One is that the researcher started a project and had some configuration problem and restarted from the beginning. That is discouraged, but some do it instead of restarting with a new project number.

The other possibility is a server problem causing reissue of WUs that have been completed in the past.

So far Gen 17 and 18 have only been completed once. For the older generations the first completion was several weeks ago.

[muziqaz]

In this case there is no display bug. There are two possibilities here. One is that the researcher started a project and had some configuration problem and restarted from the beginning. That is discouraged, but some do it instead of restarting with a new project number.

The other possibility is a server problem causing reissue of WUs that have been completed in the past.

So far Gen 17 and 18 have only been completed once. For the older generations the first completion was several weeks ago.

3rd possibility: client imagines that there is duplicate work done, while in reality it isn't.
This one is Justin's project. It is safe to say he did not mess up the settings or released another project under same project number. He himself told us, that there is no duplicate WUs on the server, even though client reports that duplicates have been sent out

[Joe_H]

The app for checking WUs is reporting multiple returns, that would be a problem on the stats server. That is not a client issue.

[muziqaz]

The app for checking WUs is reporting multiple returns, that would be a problem on the stats server. That is not a client issue.

You are correct. Though users usually see these kind of things within the client's WU History section.
Either way, I sent this to Justin, will see what he digs out

[jjmiller]

Hi all,

Thanks Mactin for reporting this. At the moment we're thinking this is tied to a bunch of server havoc that happened on/around Oct 1. Several servers went down unexpectedly, causing work to pile up on collection servers and then as they came back online all the servers became overloaded trying to transfer all the work around. I've gotten a few reports directly on other projects that this happened to at the same time, namely 18242.

At the moment we're not sure what is causing this, but are suspicious that there's a bug somewhere in the server code that's causing specific RUNxCLONEs of a project to be reset to GEN0. It seems like this is an isolated incident at this time as it only happened immediately after the server chaos.

Unfortunately though this is "duplicate" work (as in the WU were folded in the past), it is actually necessary work as the server deleted those prior WU.