zephyrproject-rtos/zephyr

tests: posix: common: separate into smaller testsuites

Open

#79,454 opened on 2024年10月5日

GitHub で見る
 (9 comments) (0 reactions) (1 assignee)C (15,249 stars) (9,144 forks)batch import
EnhancementGood first issuearea: POSIXarea: Tests

説明

Is your enhancement proposal related to a problem? Please describe. The posix.common testsuite contains a lot of mostly unrelated testsuites. As a result, the code size is large, but mostly the data size is extremely large.

It would require less variation from default settings, and would reduce ram requirements to split that testsuite into smaller groups of more closely related testsuites.

Describe the solution you'd like

The obvious way to group related testsuites is by Option Group.

E.g.

  • POSIX_BARRIERS - #81487
  • POSIX_C_LIB_EXT - #81488
  • POSIX_RW_LOCKS - #80943
  • POSIX_SEMAPHORES - #80964
  • POSIX_SIGNALS - #80930
  • POSIX_SINGLE_PROCESS - #80981
  • POSIX_SPIN_LOCKS - #80965
  • POSIX_SYSTEM_DATABASE - #81489
  • POSIX_THREADS_BASE - #81491
  • POSIX_THREADS_EXT - #81490
  • POSIX_TIMERS - #80807
  • XSI_REALTIME - #83634
  • XSI_REALTIME_THREADS - #86042
  • XSI_SYSTEM_LOGGING - #80986
  • XSI_THREADS_EXT - #81741

and potentially others.

testcase.yaml permutations can be designed to enable or disable features that affect different Option Groups, like TSS, TSA, TSH (see Codes).

Additionally, such a grouping would theoretically improve bug attribution capabilities; if an error was traced (either via stacktrace or bug description) to a certain posix function, there would be a 1:1 correspondance to an Option Group, so typically, only that testsuite would need to be executed.

Describe alternatives you've considered The way the testsuite has been designed historically.

Additional context This came up in the context of #79443 but it was already thought of as a nice-to-have.

コントリビューターガイド

技術スタック
c
領域
testing
Issue 種別
refactor
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
active
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
knowledge of Zephyr test infrastructureunderstanding of option groupsbasic C
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
60
調査方針
The issue proposes splitting the 'posix.common' testsuite into smaller groups based on Option Groups. Several sub tasks are already completed and linked (e.g., #81487, #81488, etc.). The remaining tasks are: POSIX SYSTEM DATABASE (#81489), POSIX THREADS BASE (#81491), and XSI REALTIME THREADS (#86042). To contribute, examine the existing PRs for patterns (e.g., #81487) and apply similar grouping for the remaining option groups. The test configuration should involve updating testcase.yaml with appropriate permutations for enabling/disabling features from the relevant Option Group.