We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The test "mem_pool_threadsafe" sporadically hangs forever when run with qemu_cortex_m3.
This causes sporadic CI failures.
It does so about 30% of the time.
Steps to reproduce:
git checkout 8fc5fd5 $ZEPHYR_BASE/scripts/sanitycheck -T$ZEPHYR_BASE/tests/kernel/mem_pool/mem_pool_threadsafe -p qemu_cortex_m3
Repeat up to 5 times or so if it does not trigger immediately.
To speed up the testing apply this patch:
diff --git a/tests/kernel/mem_pool/mem_pool_threadsafe/testcase.yaml b/tests/kernel/mem_pool/mem_pool_threadsafe/testcase.yaml index dfa0450076..662b080981 100644 --- a/tests/kernel/mem_pool/mem_pool_threadsafe/testcase.yaml +++ b/tests/kernel/mem_pool/mem_pool_threadsafe/testcase.yaml @@ -1,3 +1,4 @@ tests: kernel.memory_pool: tags: kernel mem_pool + timeout: 10 # Observed to run in 5 sec
The text was updated successfully, but these errors were encountered:
AFAICT this is not a recent regression, but something that has been able to happen for a long time, at least before 1.11.0.
So perhaps it has always been sporadically failing.
Sorry, something went wrong.
I was able to reproduce this in 8fc5fd5 but not in current master, I think some recent fixes @andyross made to mem pools fixes this as well. Closing.
andrewboie
No branches or pull requests
The test "mem_pool_threadsafe" sporadically hangs forever when run with qemu_cortex_m3.
This causes sporadic CI failures.
It does so about 30% of the time.
Steps to reproduce:
git checkout 8fc5fd5
$ZEPHYR_BASE/scripts/sanitycheck -T$ZEPHYR_BASE/tests/kernel/mem_pool/mem_pool_threadsafe -p qemu_cortex_m3
Repeat up to 5 times or so if it does not trigger immediately.
To speed up the testing apply this patch:
The text was updated successfully, but these errors were encountered: