diff options
| author | Paul Buetow <paul@buetow.org> | 2026-05-31 09:55:02 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2026-05-31 09:55:02 +0300 |
| commit | e8948e9f52235cbbbd8af098bc624bc20e173e6c (patch) | |
| tree | 75fac81f5121cfdaac5234cca371a126be52cdb4 /integrationtests/retbytes_test.go | |
| parent | 75d00f479d333476990ff18f7427905bb09d49f0 (diff) | |
test(aio): add io_setup end-to-end integration coverage
The classic Linux AIO family (io_setup/io_submit/io_getevents/io_cancel/
io_destroy) had no integration coverage: family_test.go exercises only
FS/Memory/IPC/Network/Process/Sched/Time, and iouring_test.go covers only
the distinct io_uring_* family. io_setup is classified KindNull/FamilyAIO,
which is correct by inspection against man 2 io_setup (nr_events is a count,
ctx_idp an output pointer, so no fd/path is captured), so the tracer itself
needed no change.
Add an ioworkload AIO scenario that drives io_setup(2)/io_destroy(2) raw
(no privileges, no libaio) plus an EINVAL variant, and integration tests
that assert ior records the enter_io_setup tracepoint end-to-end, mirroring
the existing iouring scenario/test pattern.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Diffstat (limited to 'integrationtests/retbytes_test.go')
0 files changed, 0 insertions, 0 deletions