Skip to content

Mention logging with ERROR level when using --exitonerror #5388

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 7, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions doc/userguide/src/ExecutingTestCases/TestExecution.rst
Original file line number Diff line number Diff line change
Expand Up @@ -692,6 +692,11 @@ fatal and execution stopped so that remaining tests are marked failed. With
parsing errors encountered before execution even starts, this means that no
tests are actually run.

When this option is enabled, using `ERROR` level in logs, such as `Log` keyword
from BuiltIn or Python's standard logging module, will also fail the execution.
Additionally, the TRY/EXCEPT stucture does not catch log messages with `ERROR`
level, even when :option:`--exitonerror` is used.

__ `Errors and warnings during execution`_

Handling teardowns
Expand Down