Skip to content

Conversation

@csviri
Copy link
Collaborator

@csviri csviri commented Dec 22, 2025

Signed-off-by: Attila Mészáros a_meszaros@apple.com

Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
@openshift-ci openshift-ci bot requested review from metacosm and xstefank December 22, 2025 09:06
@csviri csviri linked an issue Dec 22, 2025 that may be closed by this pull request
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
workflowExecutor.handleExceptionInExecutor(dependentResourceNode, e);
} catch (Error e) {
// without this user would see no sign about the error
log.error("java.lang.Error during execution", e);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we also add it to the incremental recording of error messages that the workflow keeps?

Copy link
Collaborator Author

@csviri csviri Dec 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should not, this is just for a corner case, where we receive Errors. Those should not be caught in general in Java, and indicate a fundamental issue. Think of receving here an OutOfMemoryError. But also from the original reported issue the NoSuchFieldError indicates an issue with the bytecode. So we simply should not handle it.

@csviri csviri merged commit 9f6c8c1 into main Dec 22, 2025
25 checks passed
@csviri csviri deleted the exception-logging branch December 22, 2025 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error handling for Dependents is incomplete

3 participants