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

12 lines
224 B
Plaintext
Raw Normal View History

tests: POSIX: Refactor POSIX API tests Refactor and club the POSIX API tests into one test suite. Signed-off-by: Spoorthi K <spoorthi.k@intel.com>
2018-09-18 18:37:58 +08:00
CONFIG_PTHREAD_IPC=y
CONFIG_POSIX_API=y
CONFIG_MAX_PTHREAD_COUNT=20
CONFIG_ZTEST=y
CONFIG_SEM_VALUE_MAX=32767
CONFIG_POSIX_MQUEUE=y
CONFIG_HEAP_MEM_POOL_SIZE=4096
tests: set CONFIG_MAX_THREAD_BYTES for a few tests Some tests instantiate a lot of thread objects. These were not tagged with __kernel, and CONFIG_APPLICATION_MEMORY was enabled, so the kernel was not adding them to the kernel object database. However, with CONFIG_APPLICATION_MEMORY disabled, this overflowed the default max number of thread objects (16). Increase the max to 32 for these particular tests. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2019-02-01 07:09:41 +08:00
CONFIG_MAX_THREAD_BYTES=4
pthread: add setname/getname glibc extensions Adding the ability to set and get pthread names by defining some non-standard extension functions that were first introduced by Glibc. Similar to zephyr thread naming, these allow for thread tracking and debugging even when using the more portable posix API. Though Glibc was the originator, the current POSIX functions have return codes based on Oracle's adopted spec, so these functions follow suit. The Oracle and Glibc function prototypes match. Signed-off-by: Nicholas Lowell <nlowell@lexmark.com>
2020-02-15 04:12:03 +08:00
CONFIG_THREAD_NAME=y
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_SMP=n