Development for LHC@home

I tested enough. No problems seen

Do you plan to pass this new version to Lhc@Home?

It has been there but there was a very high error rate which needs to be investigated.
If the configuration changes made here lead to a stable app_version I'm sure David will transfer it to the prod server.

"But i prefer an OFFICIAL app from the project."
My guess would be this will happen in weeks, months, maybe never there.

I like beta test, but stable app is better!!
:-P

It has been there but there was a very high error rate which needs to be investigated.

I don't understand. You said there are a lot of errors and Crystian said there are not problems....

See David's post here:
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5867&postid=46960

One error is now sorted out but it needs more testing to be sure there isn't another one.

I tested enough. No problems seen: https://lhcathomedev.cern.ch/lhcathome-dev/results.php?hostid=4600&offset=0&show_names=0&state=0&appid=5

Although these were all single running 2-core tasks. I'll try tomorrow to run some tasks concurrently on my other host which has morre RAM.

I tested this morning 23 tasks running up to 6 concurrently.

I can't find anything suspicious that this application would prevent it from going into production.
I don't have a linux system, so no test results with the Linux VBox version.

https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3097010
Running 3 hours with production Atlas-Tasks.
Seem got no input.

https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3097010
Running 3 hours with production Atlas-Tasks.
Seem got no input.

I wouldn't run an almost three years old VirtualBox version combined with a Windows 10 or 11 Pro OS.
That's asking for troubles.

Alright, but the only one for me, because the test of original Boinc-Homepage, sorry.

Got for the Threadripper a new .vdi with a timestamp from today 3:30 UTC for production.

I wouldn't run an almost three years old VirtualBox version combined with a Windows 10 or 11 Pro OS.
That's asking for troubles.

No problem here with Win11 and VirtualBox 6.1.32

Got for the Threadripper a new .vdi with a timestamp from today 3:30 UTC for production.

There is no new ATLAS-vdi since 30 Jun.
Maybe what you noticed is an updated modification date for that file. The creation date should be of the first time you got the .gz-file from the server.

Every time when VBoxSVC.exe is not running and you get an ATLAS-task, the modification time of ATLAS_vbox_1.13_image.vdi is updated for the new (multi)attach to that file to create a differencing vdi-file into the snapshot directory.

This is in production, not -dev.
Is it possible to rename the vboxwrapper_26204_windows_x86_64 to vboxwrapper_26198ab7_windows_x86_64 and see what happens?

I did not realized that 'for production', you meant LHC@home.
Maybe your 'new' vdi is just the old one, replacing v1.13 which runs a few days last week, but is withdrawn, because of too much errors.
Just wait until the dev-version will come into production at LHC@home.

Yes, LHC@Home,
ok, will wait until -dev Version is tranfered.
atm Threadripper running well.

FATAL: Could not read from the boot medium! System halted.
https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3097187

I have submitted a bunch of 100 tasks with 20 events each, to generate some load.

If those finish too quickly I can generate more on demand.

I have submitted a bunch of 100 tasks with 20 events each, to generate some load.

If those finish too quickly I can generate more on demand.

Thank you, David.

Are these tasks scientifically useful or do we get them only for testing the new application?

There still appears to be a conflict when running LHC and -dev together. I tried a few LHC over the weekend and THEY run fine but new -dev tasks all stopped with a similar error. Setting No New Tasks and allowing the LHC ones to finish, I then exited Boinc, deleted everything in the slots and removed the .vdi from VBox, then closed the VBox window as advised previously. Restarted Boinc and all is well again with only -dev tasks running. (This is with Theory but seems it might also apply to Atlas if Maeax is running LHC and -dev)

I have submitted a bunch of 100 tasks with 20 events each, to generate some load.

If those finish too quickly I can generate more on demand.

Thank you, David.

Are these tasks scientifically useful or do we get them only for testing the new application?

The outputs of these tasks are not used for any science, but you can think of your contribution here as helping to improve the way we get science results out of the tasks on the production project.

Seems those 100 tasks went out quickly, so I put another 200 in.