there is a suspicion that an old copy of the application has replaced a new one
old hosts generate a runtime error with the following characteristics:
- text output Hello, stderr!
- file result.txt is missing

it is desirable to introduce some kind of system for the uniqueness of applications and their versions

Also getting a lot of download errors.

Hi,

I understand the application version problem.

In the application 1_Gaia@home I used <sticky/><no_delete/> for 2 files.
After 3000 jobs I will change this 2 file.
I can give new names, but the old ones will stay in client disc space.
Is it possible to remove them?

Is it possible to remove them?

https://boinc.berkeley.edu/trac/wiki/DeleteFile

You can create a file file_delete_regex in your project directory, containing a list of regular expressions, one per line.
If a client has a sticky file whose name matches any of these expressions, it will be instructed to delete the file.

note - wait until all tasks with these files are completed and will report

FYI, still getting occasional download errors.

Not so "occasional" for me :( They're all failing on download.

---

this is my personal opinion,
but I would like to have a stable set of applications, it is better to use numbers for different versions.

volunteers are mainly focused on collecting statistics (both total and separately for applications),
for example, to obtain achievement levels - badges.
with one-day numbered apps it makes no sense :o(

it is important for you as an administrator to have a tool convenient for your purposes.
but I hope you can take this opinion into account when planning the structure of a distributed project

[upd]
you can use batch number for subsets of jobs with different datasets
application name and version displays stability and minor improvements in the executable file code

examples with batch numbers can be found at neighbors - cpdn and tomas brada projects

Just wondering why so many download errors? Getting heaps of them.

Smile and enjoy your day
Conan

---

Sorry for the large number of tests, but we have a problem with getting the correct precision of numerical calculations ......

Well, keep trying :) I'm here to test as many batches as you need!

---

many download errors ...... - fixed

Due date for the latest batch is way too short. Causing BOINC to go into panic mode.

yes - needs to be more than 24 hours to avoid issues.

also, limiting tasks to client core count is too harsh - my clients fetched other works instead because of this - suggest reverting to at least 2 tasks/core like yesterday.

download errors do appear to have been solved though.