Currently we have the windows applications broken. We are looking into it.

Linux and CPU jobs work fine

Thanks, but all the GPU work has been cancelled for Linux also. Maybe you could add some back?

I have now deprecated the Windows apps, so we can put some more work for Linux

We are trying to create a new app for Windows, but it might take few days.

gdf

PS: can you post here some of the WU failed for Windows so that I can easily find the error message?

We are trying to create a new app for Windows, but it might take few days.

gdf

PS: can you post here some of the WU failed for Windows so that I can easily find the error message?

PS: can you post here some of the WU failed for Windows so that I can easily find the error message?

Error message is always the same..

<core_client_version>7.10.2</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -44 (0xffffffd4)</message>
]]>

take some of my recent ones.
https://www.gpugrid.net/results.php?userid=146761

---

I would love to see HCF1 protein folding and interaction simulations to help my little boy... someday.

Thanks for the update, GDF. Noticed this yesterday on my 2 Win boxes. Here's a couple of the errors:

https://www.gpugrid.net/result.php?resultid=18149877

Stderr output
<core_client_version>7.10.2</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -44 (0xffffffd4)</message>
]]>


https://www.gpugrid.net/result.php?resultid=18146999

Stderr output
<core_client_version>7.10.2</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -44 (0xffffffd4)</message>
]]>

Good luck sorting it out...

Cheers!

We had the same error number (I searched for 0xffffffd4) and the same symptoms - every task failing on Windows machines, for one of the Windows apps, at the same time - on 14/15 April 2017.

The conclusion reached in all WUs downloaded recently produce "computation error" right away (that's last years thread, not the similarly named thread this week) was that the licence for one component included in the app had expired.

I think if all UTs generate the same error, it should be pretty simple.

Good luck to fix!

Thanks, but all the GPU work has been cancelled for Linux also. Maybe you could add some back?

This is still the case. Now everyone is doing nothing.

I just got 243000 credits for a GPU task on my main Linux box.It and the the Linux laptop are running QC tasks.
Tullio

Could someone please explain this? (Windows hosts still receive and fail GPU workunits, while the Windows app is deprecated)

Just caught myself a couple of those on my mine canary - the one which will tell me when good work starts to flow again.

I think it may result from a mis-understanding of what it means to 'deprecate' an application in the BOINC world. There are other oddities, like a string of

21/07/2018 00:16:01 |  | [unparsed_xml] FILE_REF::parse(): unrecognized: 'rboinc/'

in the log - one for every downloaded task file. They look like

<file_ref>
<file_name>e46s10_e41s8p0f164-ADRIA_FOLDT1008_v2_predicted_pred_ss_contacts_50_T1008_2-0-LICENSE</file_name>
<open_name>LICENSE</open_name>
<rboinc/>
</file_ref>

<rboinc/> is meaningless in that context and shouldn't be there.

A volunteer effort. doubtless "Measure twice cut once" at this time.

Possibly related to the thing that derailed BOINC,
some new windows patch. ??

... (Windows hosts still receive and fail GPU workunits, while the Windows app is deprecated)

this seems to explain why on the Server Status Page the tasks show error rates of 81% and higher.

I had been running the Windows App on my fastest system successfully after the 14th July license problems (which occur annually but seem to take you by surprise every time) by turning my system time back. However, now you seem to have deprecated it and I get nothing.

I am continually disappointed by the way this project is run.

---

Radio Caroline, the world's most famous offshore pirate radio station.
Great music since April 1964. Support Radio Caroline Team -
Radio Caroline

I had been running the Windows App on my fastest system successfully after the 14th July license problems (which occur annually but seem to take you by surprise every time) by turning my system time back. However, now you seem to have deprecated it and I get nothing.

How come you didn't tell us to set the time back before? We could've kept crunching

Yes, sorry that I didn't. However, the problem is a recurring one and I thought everyone knew from the last time it happened.

---

Radio Caroline, the world's most famous offshore pirate radio station.
Great music since April 1964. Support Radio Caroline Team -
Radio Caroline

We just have to be patient for the scientists to fix the problems. In the meantime, some other GPU projects I'm attached to (with 0 resource share, as backup projects), are getting some extra work done for them :)

If your running other projects other than GPUGrid, I would strongly recommend that you don't set your clock back, you could get validation errors or WU's canceled because of deadline over-run.