Skip to content

Conversation

@f3sch
Copy link
Collaborator

@f3sch f3sch commented Sep 12, 2025

If we are catching the expected exception std::bad_alloc, the print is superfluous. Also the validation script explicitly regex checks the log for this string leading to jobs being failed although the reco was successful. If the exception is anything different, still print it.

If we are catching the expected exception std::bad_alloc, the print is superfluous. Also the validation script explicitly regex checks the log for this string leading to jobs being failed although the reco was successful.
If the exception is anything different, still print it.
@github-actions
Copy link
Contributor

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

@mconcas mconcas merged commit cb96bdb into dev Sep 13, 2025
13 checks passed
@mconcas mconcas deleted the f3sch-patch-2 branch September 13, 2025 06:45
shahor02 pushed a commit to shahor02/AliceO2 that referenced this pull request Sep 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants