tools/testing/selftests/kselftest_harness/harness-selftest.expected
Source file repositories/reference/linux-study-clean/tools/testing/selftests/kselftest_harness/harness-selftest.expected
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/kselftest_harness/harness-selftest.expected- Extension
.expected- Size
- 3802 bytes
- Lines
- 99
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: tools
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
TAP version 13
1..19
# Starting 19 tests from 4 test cases.
# RUN global.standalone_pass ...
# harness-selftest.c:19:standalone_pass:before
# harness-selftest.c:23:standalone_pass:after
# OK global.standalone_pass
ok 1 global.standalone_pass
# RUN global.standalone_fail ...
# harness-selftest.c:27:standalone_fail:before
# harness-selftest.c:29:standalone_fail:Expected 0 (0) == 1 (1)
# harness-selftest.c:30:standalone_fail:Expected 0 (0) == 1 (1)
# standalone_fail: Test terminated by assertion
# FAIL global.standalone_fail
not ok 2 global.standalone_fail
# RUN global.signal_pass ...
# harness-selftest.c:35:signal_pass:before
# harness-selftest.c:37:signal_pass:after
# OK global.signal_pass
ok 3 global.signal_pass
# RUN global.signal_fail ...
# harness-selftest.c:42:signal_fail:before
# harness-selftest.c:43:signal_fail:Expected 0 (0) == 1 (1)
# signal_fail: Test terminated by assertion
# FAIL global.signal_fail
not ok 4 global.signal_fail
# RUN global.exit_pass ...
# OK global.exit_pass
ok 5 global.exit_pass
# RUN global.exit_xpass ...
# OK global.exit_xpass
ok 6 global.exit_xpass # XPASS unknown
# RUN global.exit_fail ...
# exit_fail: Test failed
# FAIL global.exit_fail
not ok 7 global.exit_fail
# RUN global.exit_xfail ...
# OK global.exit_xfail
ok 8 global.exit_xfail # XFAIL unknown
# RUN global.exit_skip ...
# OK global.exit_skip
ok 9 global.exit_skip # SKIP unknown
# RUN global.test_result_pass ...
# OK global.test_result_pass
ok 10 global.test_result_pass
# RUN global.test_result_xpass ...
# OK global.test_result_xpass
ok 11 global.test_result_xpass
# RUN global.test_result_fail ...
not ok 1 # Illegal usage of low-level ksft APIs in harness test
# test_result_fail: Test failed
# FAIL global.test_result_fail
not ok 12 global.test_result_fail
# RUN global.test_result_xfail ...
# OK global.test_result_xfail
ok 13 global.test_result_xfail
# RUN global.test_result_skip ...
# OK global.test_result_skip
ok 14 global.test_result_skip
# RUN fixture.pass ...
# harness-selftest.c:53:pass:setup
# harness-selftest.c:62:pass:before
# harness-selftest.c:19:pass:before
# harness-selftest.c:23:pass:after
# harness-selftest.c:66:pass:after
# harness-selftest.c:58:pass:teardown same-process=1
# OK fixture.pass
ok 15 fixture.pass
# RUN fixture.fail ...
# harness-selftest.c:53:fail:setup
Annotation
- Atlas domain: Support Tooling And Documentation / tools.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.