Not sure if this is something Boinc is not doing, or a problem with Ralph.

A task https://ralph.bakerlab.org/result.php?resultid=5433248 was sent to me with the usual 3 day deadline, but it ran for 5 days, using 100% of a CPU core. I eventually gave up and aborted it, even though you say not to abort them, as this one looked like it would go on indefinitely. I assumed it would have useful information in stderr for you to work out why it was stuck in a loop, but the information is not there. Strangely on my task list https://ralph.bakerlab.org/results.php?userid=86770 it shows as 0 CPU time, which is untrue, it was using a whole core for 5 days.

However this one https://ralph.bakerlab.org/result.php?resultid=5432455 shows plenty information.

Also posted to Github Boinc issues: https://github.com/BOINC/boinc/issues/5425

A request from the Boinc folk:

"VBox log is written to the separate file, and IIRC this file is usually transferred to the server when WU is aborted. However, the information from this file is usually not shown on the web UI.
It would be nice here to clarify from the Project admins that they have received all the logs, and if this is true - then this ticket could be closed."

It's essential to ensure transparent communication between BOINC users and project administrators regarding log file transfers and visibility on the web UI for comprehensive troubleshooting. Clarifying receipt of all logs and addressing any discrepancies would streamline the resolution process and enhance user satisfaction. Additionally, individuals seeking SVG Mardi Gras graphics can explore online resources to find vibrant and festive images.