Good news. The machine which failed yesterday is now running an acemd3 cuda101 task. Here is the full set of C runtime library files, and where they're being run from:



I'll drop a line to Gianni, to pass on to the development / deployment team.

I'll drop a line to Gianni, to pass on to the development / deployment team.

any reaction from their side so far ?

Sadly, none at all. I might try Toni, after our conversation in the news thread yesterday.

This is already fixed in acemdbeta and will be fixed as soon as we deploy the new app.

Sadly, I'm not completely convinced by this.

My host 43404 ran one of the Beta tasks on 29 September. I have two downloaded files from that day in my project directory:

windows_x86_64__cuda101.zip
job.xml

Significantly, there is no new conda-pack.zip: that file is still dated 20 September.

I've examined the new acemd3.exe file from the zip - dated 27 September - using Dependency Walker. That still shows vcruntime140_1.dll as a required file, invoked by msvcp140.dll

My machine has the full triple-pack of VC runtime files installed, so this may be an artifact of that. Did anyone get one of the Beta test jobs, without having the manual VC runtime pack installed. Did it run successfully?

I didn't manually intervene with anything and got 3 beta tasks that ran successfully on my Win10 machine. They all finished successfully within a few minutes. Does that help?

That's reassuring - thanks. But I'll keep an eye on my Windows 7 machines when the project next ramps up.

This is already fixed in acemdbeta and will be fixed as soon as we deploy the new app.

No further explanation ?
How can we fix it ? What is the problem ?
Not only the C++ (I have all dll and C++ manually installed)
Till june all was working. Now, not more (without any change in my config.
It seems the problem comes from the WU