logging: log_core: regression in handling of CONFIG_LOG_BLOCK_IN_THREAD_TIMEOUT_MS #63965
Labels
area: Logging
bug
The issue is a bug, or the PR is fixing a bug
priority: medium
Medium impact/importance bug
Regression
Something, which was working, does not anymore
Describe the bug
With deferred logging, the
CONFIG_LOG_BLOCK_IN_THREAD_TIMEOUT_MS
was introduced in order to block the log processing thread and preserve all messages.For reference, the blocking feature was described in #15196 and added in #16194. Then the logging v2 API was added in f6a40ae which did not carry-over the feature / fix.
There does not seem to be any test coverage for this feature though, and a regression appeared that would hang systems.
Please also mention any information which could help others to understand
the problem you're facing:
To Reproduce
west build -p auto -b tests/subsys/logging/log_blocking/
Expected behavior
The testsuite should succeed with all permutations specified in the
testcase.yaml
provided.Impact
This has been a massive pain point for us, since logging behaviour changed quite unexpectedly in the v2.x series.
Per policy, not just for diagnostics, we need enable the collection of logs from our devices, and nobody had been able to narrow down why this changed for .. quite a while. We have been evaluating 3.x releases recently in order to prepare moving from LTSv2. This was the one regression that is holding us back.
Logs and console output
Working on a testsuite at the moment, but the simplest way to reproduce this would be to verify the following failure in any testsuite.
There is no test coverage to point to (yet)
Environment (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: