Hi everyone,

If you encounter a problem with xoroshigo2 (v1.1), please chime in on this thread.

Helpful info for us to have:
1. Example task where the issue occurred
2. The contents of stderr_file (can be found in the slot directory running the app)
3. The contents of stdout_file (can be found in the slot directory running the app)

Please include as much of this as possible as this gives us the greatest chance of diagnosing your particular issue and publishing a fix.

Thank you!

4 Apr 2025, 15:06:59 UTC 4 Apr 2025, 23:44:40 UTC Erreur lors des calculs 2,193.89 2,078.34 --- Xoroshiro128++ Guessing Order Optimization v1.1 v1.02
windows_x86_64

Stderr output

<core_client_version>8.0.2</core_client_version>
<![CDATA[
<message>
Le syst�me d�exploitation ne peut pas ex�cuter (null).
(0xc3) - exit code 195 (0xc3)</message>
<stderr_txt>
2025-04-05 01:06:24 (16868): wrapper: running .\client-windows.exe ( config-003-hxlreg-fullinfo-rank100.npz 30000000 459 input.npz)
2025-04-05 01:06:25 (16868): wrapper: created child process 15068
2025-04-05 01:42:51 (16868): .\client-windows.exe exited; CPU time 2078.343750
2025-04-05 01:42:51 (16868): app exit status: 0xc2
2025-04-05 01:42:51 (16868): called boinc_finish(195)

</stderr_txt>
]]>

I have 9x Raspberry Pi, or Pi clones. 8 of the 9 are completing tasks just fine. But this one gets nothing but errors:

https://minecraftathome.com/minecrafthome/show_host_detail.php?hostid=28336

Here is a sample of the Stderr output:

<core_client_version>7.18.1</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)</message>
<stderr_txt>
2025-04-05 01:04:50 (14416): wrapper (8.1.26018): starting
2025-04-05 01:04:50 (14416): wrapper: running ./client-linux-arm64.bin ( config-004-hixorlo-fullinfo-rank080.npz 30000000 3720 input.npz)
2025-04-05 01:04:50 (14416): wrapper: created child process 14418
2025-04-05 01:04:51 (14416): ./client-linux-arm64.bin exited; CPU time 0.428000
2025-04-05 01:04:51 (14416): app exit status: 0x4
2025-04-05 01:04:51 (14416): called boinc_finish(195)

</stderr_txt>
]]>

Any ideas about what is problem is?

It's hard to say what's wrong without the contents of stderr_file in a slot directory that failed.

Can you find that and share it here?

It's hard to say what's wrong without the contents of stderr_file in a slot directory that failed.

Can you find that and share it here?

it can be difficult to get files from the slot directory after a failure since they are all deleted the instant the task finishes. might be easier to instruct users how to run the app offline so that it's not deleted by BOINC when the task finishes

... Can you find that and share it here?

it can be difficult to get files from the slot directory after a failure since they are all deleted the instant the task finishes. might be easier to instruct users how to run the app offline so that it's not deleted by BOINC when the task finishes

I have had same experience as Ian - content of slots directory disappear nearly instantly upon crashing.

Providing detailed manual running instructions OUTSIDE OF BOINC would be appreciated so we can help you out.

expect an app update that fixes this "soon"

I've tried Ian's test package with the stock binary on my Jetson TX2-NX SoC but it fails instantly and doesn't leave any stderr.txt fle in the test directory for debugging information. Just leaves the downloaded numpy support directory.

I'm currently testing his fixed test binary that is running now and will report back when it is finished.

my odroids are now running version 1.03 of the v1.1 app and it looks good

My test task using the new test application just finished after 2 hours 20 minutes on my Nvidia Jetson TX2-NX.
contents of output.txt
keith@tx2-nx:~/Downloads/test$ cat output.txt
68.023209
806778377d6b82ff04d0009d24e24481020f813500158f2e2931911780329016
config-003-hxlreg-fullinfo-rank100.npz 30000000 8840
127 30191000

The issue with select ARM-based devices should now be resolved.

Thanks for everyone's help with that! :)

The issue with select ARM-based devices should now be resolved.

Thanks for everyone's help with that! :)

Thanks!