Development for LHC@home

OK, OK, 3 of them finally terminated with similar duration by awarding 1k-1,5k credits, but that one is my record :)

That is about right since the run time and CPU time are around 33 hours.
As far as them running at 100% that is how the tend to run but I wouldn't let one run like that for over 45 hours total.
I would abort if they did that and last time I got some to run I watched the CPU to see if it even seemed to be doing anything.

So far that worked BUT I haven't been able to get any more since I only got 4 and then all the rest were taken......which is too bad since I run them as fast as possible and turn them in so we don't have to wait for weeks.

But I did see a strange one that ran for 19 hours and got 1.27 Credit

They released, yesterday, a new version of Xboinc (0.03)
I don't know if this version will be released here in test to solve some problems....

It looks like Freddie is working on that and I hope we get some to run here soon.

It looks like Freddie is working on that and I hope we get some to run here soon.

They don't seem to be in a hurry :-P

They don't seem to be in a hurry :-P

Yeah you would think this is December again or they forgot we are here waiting every day.

---

Mad Scientist For Life

They released, yesterday, a new version of Xboinc (0.0.3)

The new version of Xboinc is 0.1.2
Waiting for some new wus here...

The new version of Xboinc is 0.1.2

And 0.1.3 is ready:
- Important bugfix in executable
- Added tests

Version 0.11 is the first.

We are waiting for work to crunch!

1 year ago...
We are still waiting :-P

And 0.1.3 is ready

Now the version is 0.1.5

No more compilation at import (default tracker is cached and only compiled when needed)
Xsuite environment versions are only asserted when needed
Fixed internal versioning scripts
Updated examples and tests (tests do not enforce xsuite versions, to make sure issues are found)

Another bunch of test tasks are sent to us volunteers without any communication.
I suppose this time the tasks are coming from researcher Frederik Van der Veken.
The tasks however are useless to test, because they all don't really start and all crash within a few seconds with too many exits.

I received 1 on a PC hat has been running for 17 hours.
Another PC received several that error'd immediately with segmentation violation.

All while someones been running 3 tasks since Nov per WUProp hour data.

Edit:
Now the PC with 17 hour task received some more but all failed:

<core_client_version>7.16.6</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)</message>
<stderr_txt>
SIGSEGV: segmentation violation
Stack trace (8 frames):
[0x42f3c0]
[0x44b5b0]
[0x408b46]
[0x40900e]
[0x429157]
[0x429e7f]
[0x4cd58e]
[0x402265]

Exiting...

</stderr_txt>
]]>

Same for me mostly segmetation fault.

There was one good one, almost

<core_client_version>7.24.1</core_client_version>
<![CDATA[
<stderr_txt>
2024-01-12 18:06:25 (5864): called boinc_finish(0)

</stderr_txt>
<message>
upload failure: <file_xfer_error>
<file_name>fvanderv__fulltest1__job0__O457o6glrgwX_1_r1723837928_result</file_name>
<error_code>-161 (not found)</error_code>
</file_xfer_error>
</message>
]]>

Server says we have some but all I got one and it didn't do anything 10 hours ago

I got some but all of them segfaulted on my vmware vm.

https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3289937

I got some but all of them segfaulted on my vmware vm.

But there are valid wus??
I read only errors....

At the end, i can attach a linux machine to lhc-dev to test Xtrack
Obviously all errors on my Mint 20 pc

<message>
process exited with code 193 (0xc1, -63)</message>
<stderr_txt>
SIGSEGV: segmentation violation
Stack trace (8 frames):
[0x42f3c0]
[0x44b5b0]
[0x408b46]
[0x40900e]
[0x429157]
[0x429e7f]
[0x4cd58e]
[0x402265]

Exiting...

Still all errors
Please, stop this batch and fix the problem

Please, stop this batch and fix the problem

Seems they are working on the code.
Waiting for a new app and a new batch of wus

Since last June when we had the ones that seemed to work I wondered why those aren't good enough to run doing those or why they just appeared to be Valids and didn't do what we want them to do.
(without digging around github)

Wouldn't mind some CMS here to run too.......since for another mysterious reason mine have no problems with CMS but crash in 24 seconds with Theory now (here and over at prod.) I even tried to reset the project and d/l it again a few times.....but I will figure it out eventually yes I know this is a different thread but we are all regulars here so I never have a problem with that

Only good thing is most of my GPU's are busy at Einstein for the next 2 months but I do have some ready here for the Xtrack 24/7
(Hi Axel)

Yes Magic,
some time seeing -dev what's going on.
But, this is not so much.
Theory is something for Laurence, if he have time.
Atlas went also wrong for me two days ago.
Now it's running again.
And E@H like, we want to see it as volunteers.