OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/tests/kernel/threads/thread_apis/prj.conf

11 lines
235 B
Plaintext
Raw Normal View History

tests: add zephyr thread lifecycle test case with unified kernel this commit cover zephyr thread lifecycle relavant apis testing k_thread_spawn k_current_get k_thread_abort k_thread_cancel k_thread_suspend k_thread_resume Change-Id: I99bff0dd803f6e68e165f3388a3be09425c0596c Signed-off-by: jing wang <jing.j.wang@intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-12-20 16:41:43 +08:00
CONFIG_ZTEST=y
tests: abort: Testcase for repeated thread abort Test case to showcase the repeated abort of a thread. Signed-off-by: Adithya Baglody <adithya.nagaraj.baglody@intel.com>
2018-01-23 18:07:10 +08:00
CONFIG_THREAD_MONITOR=y
tests: threads: fold customdata tests into main test Move this small test to the main thread test project. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-05-24 11:47:15 +08:00
CONFIG_THREAD_CUSTOM_DATA=y
tests: test k_thread_name_set Basic test for new API: k_thread_name_set. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-08-13 04:58:43 +08:00
CONFIG_THREAD_NAME=y
tests: kernel: Move k_thread_foreach() API test to thread_apis test Move k_thread_foreach() API test from tests/kernel/profiling to tests/kernel/threads/thread_apis. Fixes #7966 Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
2018-06-04 13:28:31 +08:00
CONFIG_THREAD_STACK_INFO=y
CONFIG_HEAP_MEM_POOL_SIZE=256
tests: Mass SMP disablement on non-SMP-safe tests (Chunk 3 of 3 - this patch was split across pull requests to address CI build time limitations) Zephyr has always been a uniprocessor system, and its kernel tests are rife with assumptions and outright dependence on single-CPU operation (for example: "low priority threads will never run until this high priority thread blocks" -- not true if there's another processor to run it!) About 1/3 of our tests fail right now on x86_64 when dual processor operation is made default. Most of those can probably be recovered on a case-by-case basis with simple changes (and a few of them might represent real bugs in SMP!), but for now let's make sure the full test suite passes by turning the second CPU off. There's still plenty of SMP coverage in the remaining cases. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2019-02-23 03:45:23 +08:00
CONFIG_SCHED_CPU_MASK=y
tests: CONFIG_TEST_USERSPACE now off by default Unlike CONFIG_HW_STACK_PROTECTION, which greatly helps expose stack overflows in test code, activating userspace without putting threads in user mode is of very limited value. Now CONFIG_TEST_USERSPACE is off by default. Any test which puts threads in user mode will need to set CONFIG_TEST_USERSPACE. This should greatly increase sanitycheck build times as there is non-trivial build time overhead to enabling this feature. This also allows some tests which failed the build on RAM-constrained platforms to compile properly. tests/drivers/build_all is a special case; it doesn't put threads in user mode, but we want to ensure all the syscall handlers compile properly. Fixes: #15103 (and probably others) Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2019-04-06 06:39:50 +08:00
CONFIG_TEST_USERSPACE=y
tests: Never disable SMP Disabling SMP mode for certain tests was a one-release thing, done to avoid having to triage every test independently (MANY are not SMP-safe), and with the knowledge that it was probably hiding bugs in the kernel. Turn it on pervasively. Tests are treated with a combination of flagging specific cases as "1cpu" where we have short-running tests that can be independently run in an otherwise SMP environment, and via setting CONFIG_MP_NUM_CPUS=1 where that's not possible (which still runs the full SMP kernel config, but with only one CPU available). Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2019-08-20 23:42:43 +08:00
CONFIG_MP_NUM_CPUS=1
tests: thread_apis: add k_thread_join() tests Exercise various scenarios from thread and ISR context. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2020-02-22 05:51:57 +08:00
CONFIG_IRQ_OFFLOAD=y