Feature #2111
openmsgr workloads
Added by Sage Weil about 12 years ago. Updated over 11 years ago.
0%
Description
Develop the interfaces which will allow us to break messenger sockets at precisely-defined points.
Allow comparison between messages sent and received to verify correct transmission.
Write example tests to show how to use each capability.
Updated by Sage Weil about 12 years ago
- Translation missing: en.field_story_points set to 5
- Translation missing: en.field_position deleted (
2) - Translation missing: en.field_position set to 2
Updated by Sage Weil about 12 years ago
- Target version set to v0.44
- Translation missing: en.field_position deleted (
2) - Translation missing: en.field_position set to 1151
Updated by Sage Weil about 12 years ago
- Translation missing: en.field_position deleted (
1151) - Translation missing: en.field_position set to 1141
Updated by Greg Farnum about 12 years ago
- Status changed from New to In Progress
- Assignee set to Greg Farnum
What we're looking for here are basic tests like connect, send message, kill connection, send another message; and verify that all the received messages are correct.
These tests aren't going to involve any serious internal Pipe state, but will require at least a barebones MessengerDriver and TestDriver interface. The outline is to implement 3 orders and 4 state/event reports:
orders: connect to y; send message x to y; break connection to y
reports: new incoming connection from y; finished establishing connection to y; received message x from y; connection to y broke
Updated by Sage Weil about 12 years ago
- Target version changed from v0.44 to v0.45
- Translation missing: en.field_position deleted (
1150) - Translation missing: en.field_position set to 8
Updated by Sage Weil about 12 years ago
- Target version changed from v0.45 to v0.46
Updated by Greg Farnum about 12 years ago
- Status changed from In Progress to 4
I think the messenger tester may be at a point where we can call this bug satisfied.
Updated by Sage Weil about 12 years ago
- Target version deleted (
v0.46) - Translation missing: en.field_position deleted (
67) - Translation missing: en.field_position set to 9
Updated by Sage Weil about 12 years ago
- Target version set to v0.47
- Translation missing: en.field_position deleted (
9) - Translation missing: en.field_position set to 9
Updated by Sage Weil about 12 years ago
- Target version deleted (
v0.47) - Translation missing: en.field_position deleted (
10) - Translation missing: en.field_position set to 1
Updated by Greg Farnum about 12 years ago
- Status changed from 4 to Fix Under Review
- Assignee changed from Greg Farnum to Sage Weil
This has been sitting in my issue area for a while and it's distracting, so I'm reassigning for review. :)
Updated by Sage Weil almost 12 years ago
- Translation missing: en.field_position deleted (
26) - Translation missing: en.field_position set to 59
Updated by Sage Weil almost 12 years ago
- Translation missing: en.field_position deleted (
117) - Translation missing: en.field_position set to 129