Skip to content

test(lmbench): 引入 lmbench 测试框架集成和自动测试脚本 - #1433

Open
mistcoversmyeyes wants to merge 22 commits into
DragonOS-Community:masterfrom
mistcoversmyeyes:feat/lmbench
Open

mistcoversmyeyes wants to merge 22 commits into
DragonOS-Community:masterfrom
mistcoversmyeyes:feat/lmbench

Conversation

@mistcoversmyeyes

Copy link
Copy Markdown
Collaborator

No description provided.

@github-actions github-actions Bot added the test Unitest/User space test label Dec 3, 2025
@mistcoversmyeyes
mistcoversmyeyes force-pushed the feat/lmbench branch 6 times, most recently from 4ca963e to b5138f4 Compare December 17, 2025 15:46
@mistcoversmyeyes
mistcoversmyeyes force-pushed the feat/lmbench branch 4 times, most recently from 2edfdee to cc88ddc Compare December 18, 2025 17:32
@mistcoversmyeyes
mistcoversmyeyes force-pushed the feat/lmbench branch 2 times, most recently from 5657c94 to a05fcb8 Compare January 13, 2026 11:13
@mistcoversmyeyes
mistcoversmyeyes force-pushed the feat/lmbench branch 2 times, most recently from 8ef1628 to a9a963e Compare July 30, 2026 04:24
@mistcoversmyeyes
mistcoversmyeyes marked this pull request as ready for review July 31, 2026 11:05
@mistcoversmyeyes
mistcoversmyeyes force-pushed the feat/lmbench branch 2 times, most recently from 1f409e9 to 364364f Compare August 12, 2026 14:41
Comment thread .worktrees/feat-lmbench Outdated
@sparkzky

Copy link
Copy Markdown
Member

几个 commit 里提到的数字不太一样(8/8、31/47、32/23),想确认下以最新代码为准,现在是多少 ok / 总共多少个?有没有逐个测例的通过清单?
以及对于 failed 的那些,大概哪些是 DragonOS 内核还没实现的特性导致的,哪些是测例脚本本身的问题?

@mistcoversmyeyes mistcoversmyeyes left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's this

Something to be clean

@mistcoversmyeyes mistcoversmyeyes left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

几个 commit 里提到的数字不太一样(8/8、31/47、32/23),想确认下以最新代码为准,现在是多少 ok / 总共多少个?
由于 Full Run 的时候,中间部分测试用例会随机卡住,阻塞后续用例运行,故而每次 Full Run OK 的测试用例数目都不一样,但是大概是 31/47 这样。

mistcoversmyeyes and others added 14 commits October 3, 2026 00:16
Establish project guidance and worktree ignore rules.
…on plans

Introduce runner abstraction and metadata extraction designs and plans before implementation.
Add the full suite, portable runners, regression tests and metadata survey.
Document runner arguments, Linux execution, case authoring and calibration alongside the implementation.

Co-authored-by: Samuka007 <samuka007@dragonos.org>
Co-authored-by: sparkzky <sparkhhhhhhhhhh@outlook.com>
Package the benchmark binaries and guest scripts through Nix and DADK.

Co-authored-by: Samuka007 <samuka007@dragonos.org>
Add QEMU execution, monitoring, result collection and schema validation.
Extend the suite README with the end-to-end workflow, guest prerequisites, architecture and result schema.
Run the benchmark workflow and publish result artifacts.
Record wrapper and guest recovery validation, scope boundaries and remaining failures.
Add /usr/sbin and /sbin to the PATH exported by rcS so startup tasks and
benchmark preparation can resolve tools such as mkfs.ext4.
Comment out eight cases that panicked or returned invalid measurements during sequential DragonOS runs. Record the observed failure and guest configuration beside each exclusion.

Validated the working-tree whitelist: 39/39 successful, no failures or skips, with 512 MiB, 2 vCPUs, one sample and a 120-second timeout. The pre-existing fifo_lat exclusion and sample-count override remain unstaged.
@mistcoversmyeyes
mistcoversmyeyes force-pushed the feat/lmbench branch 2 times, most recently from dec9ee0 to fcf72db Compare October 5, 2026 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test Unitest/User space test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants