| Age | Commit message (Collapse) | Author |
|---|
|
- INTEGRATIONTESTS-PLAN.md: full design for e2e integration tests
- integrationtests/cmd/ioworkload: standalone binary with 13 I/O scenarios
- integrationtests/expectations.go: ExpectedEvent type and assertion helpers
- integrationtests/parse.go: .ior.zst parser producing TestResult
- Export IterRecord and LoadFromFile in flamegraph package
- Fix TraceId -> TraceID, StringByName returns error instead of panic
Amp-Thread-ID: https://ampcode.com/threads/T-019c8031-c106-757a-95a0-7a5457163ce7
Co-authored-by: Amp <amp@ampcode.com>
|
|
Amp-Thread-ID: https://ampcode.com/threads/T-019c8012-eaeb-768d-a264-5a704f3939ef
Co-authored-by: Amp <amp@ampcode.com>
|
|
|
|
|
|
- Remove 5 obsolete "TODO: Unit test this" comments from eventloop.go
for event types that already have comprehensive test coverage
- Keep TODO comment for FcntlEvent which still needs tests
- Reorganize TODO.md with prioritized task list based on all TODOs
found across the codebase
- Add priority levels: High (core functionality), Medium (additional
syscalls), Low (less common features), and General improvements
- Document completed tasks to acknowledge test coverage achievements
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
|
|
Implemented three test suites for eventloop filtering functionality:
1. TestCommPropagation - Verifies that comm names established via OpenEvent
are properly propagated to subsequent syscalls from the same thread ID.
2. TestEventTypeFiltering - Tests filter behavior for each event type:
- OpenEvent: Filters by both comm and path
- PathEvent: Filters by path only
- NameEvent: Filters by path (checks both oldname and newname)
- FdEvent: Filters by comm and path via eventPair
3. TestCommFilterToggle - Tests that comm filter enable/disable works correctly,
demonstrating that FdEvents without established comm names are filtered when
comm filter is enabled.
Also fixed buffer overflow issues when setting custom comm names in tests by
clearing the buffer before copying new values.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
|
|
The EnterOnlyTest was failing because FdEvents without an established
comm name are not stored in enterEvs due to comm filter logic. Updated
the test to only verify that OpenEvents (which are always stored) remain
pending.
Also updated TODO.md to mark all edge case tests as complete.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
|
|
All file descriptor lifecycle tests have been successfully implemented:
- open→read→write→close sequence tracking
- dup/dup2 file descriptor duplication
- FD removal on close
- Multiple concurrent FDs management
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
|
|
- Add test cases for FdEvent syscalls: read, write, close, fsync, ftruncate
- Add test cases for PathEvent syscalls: mkdir, unlink, creat, stat, access
- Add test cases for NameEvent syscalls: rename, link, symlink
- Add test cases for NullEvent syscalls: sync
- Add test cases for Dup3Event syscalls: dup3
All tests pass successfully, validating proper event pairing and file
object creation for each syscall type. This provides comprehensive
coverage of the eventloop's ability to handle different event types
and syscall patterns.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
|
|
- Implement makeEnterNameEvent for NameEvent syscalls (rename, link, symlink)
- Implement makeEnterNullEvent/makeExitNullEvent for NullEvent syscalls (sync, io_uring_setup)
- Implement makeEnterDup3Event for Dup3Event syscalls (dup3)
- Update TODO.md to mark helper functions as completed
All helper functions are now implemented and tests pass successfully.
This provides the foundation for comprehensive syscall testing across
all event types supported by ior.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
|
|
- Add helper functions for FdEvent, PathEvent, and RetEvent types
- Implement test cases for read, write, close, and mkdir syscalls
- Test proper event pairing and file object creation
- Validate syscall-specific behavior for different event types
This expands test coverage beyond just openat syscalls to include
file descriptor operations and path-based operations, providing a
foundation for testing all supported syscall types.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
