summaryrefslogtreecommitdiff
path: root/common/printf.c
diff options
context:
space:
mode:
authorYuval Peress <peress@chromium.org>2021-07-09 12:04:01 -0600
committerCommit Bot <commit-bot@chromium.org>2021-07-09 19:40:37 +0000
commit7dea3f0835af95710717b9370b703bdb53ce0ee3 (patch)
tree7b645d4ed07d8a86f39017dc1d5fc48360dacbbb /common/printf.c
parent54207d9ee79bd58fb8ba0cab8e7b164f08ba93e2 (diff)
downloadchrome-ec-7dea3f0835af95710717b9370b703bdb53ce0ee3.tar.gz
zmake: lazily create the logging thread
The logging thread was crashing the test_zmake.py logic that is using the TestCase class. It seems that pytest was triggering the logging thread to die (since it's set up as a daemon) when one TestCase finished running. This caused the next TestCase to run into the .start() call which crashed since we can't start the same thread multiple times. BRANCH=none BUG=none TEST=zmake testall TEST=pytest zephyr/zmake/tests Signed-off-by: Yuval Peress <peress@chromium.org> Change-Id: I389f483a1d30d4ac21aaf547cd84c8adb9d8aa24 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3017598 Commit-Queue: Keith Short <keithshort@chromium.org> Reviewed-by: Keith Short <keithshort@chromium.org>
Diffstat (limited to 'common/printf.c')
0 files changed, 0 insertions, 0 deletions