In the last few days I've seen a couple of "ce11 1.99" tasks with names like "wu_1668071663_771218" allocated on my Ubuntu 22.04.1 machine, then fail immediately with a computation error. The executables have names like: "wrapper_2022110901_windows_x86_64.exe".
Is there an issue with the allocation algorithm, or do I need to install something like WINE to handle such jobs?
Installing WINE might help to execute these tasks properly. Check if WINE is installed, or configure your system to handle Windows executables for better compatibility.
Thanks, Joseplsen. I just want to note again, per my prior post, that we don't require or recommend WINE (for the purposes of participating in Charity Engine). It should not be required. Compute tasks should be automatically dispatched to appropriate compute resources. If anyone encounters any more exceptions to this, please do post back.
In the last few days I've seen a couple of "ce11 1.99" tasks with names like "wu_1668071663_771218" allocated on my Ubuntu 22.04.1 machine, then fail immediately with a computation error. The executables have names like: "wrapper_2022110901_windows_x86_64.exe".
Is there an issue with the allocation algorithm, or do I need to install something like WINE to handle such jobs?
Hi Graham. Yes, work has been ongoing to optimize the job-scheduler, and as sometimes happens the result was, temporarily, sub-optimal :)
-- Apart from the note in your application log, though, there should have been no adverse consequences; but please let me know if otherwise.
-- And no need for anything like WINE; assignment of tasks to appropriate devices should be automatic/transparent to you.
Installing WINE might help to execute these tasks properly. Check if WINE is installed, or configure your system to handle Windows executables for better compatibility.
Thanks, Joseplsen. I just want to note again, per my prior post, that we don't require or recommend WINE (for the purposes of participating in Charity Engine). It should not be required. Compute tasks should be automatically dispatched to appropriate compute resources. If anyone encounters any more exceptions to this, please do post back.