Feature #1412
closed
qa: spec out messenger testing
Added by Sage Weil over 12 years ago.
Updated about 12 years ago.
Description
use Colin's multiprocess framework to do a messenger test for reconnects, with socket failure injects.
types:
- client->server (lossy, e.g. client/osd, client/mon)
- client->server (lossless, e.g. client/mds)
- server/server (mds, osd, mon intracluster)
- racing connections. someting like barrier, send messages to each other, make sure they both arrive, barrier, mark down, repeat.
- inject socket errors, verify all messages go through (all types)
- Target version changed from v0.35 to v0.36
- Translation missing: en.field_position set to 2
- Translation missing: en.field_position deleted (
30)
- Translation missing: en.field_position set to 65
- Translation missing: en.field_story_points set to 5
- Translation missing: en.field_position deleted (
74)
- Translation missing: en.field_position set to 74
- Target version deleted (
v0.36)
- Translation missing: en.field_position deleted (
81)
- Translation missing: en.field_position set to 1
- Translation missing: en.field_position deleted (
12)
- Translation missing: en.field_position set to 24
- Translation missing: en.field_position deleted (
77)
- Translation missing: en.field_position set to 66
- Translation missing: en.field_position deleted (
134)
- Translation missing: en.field_position set to 1
- Target version set to v0.43
- Translation missing: en.field_position deleted (
4)
- Translation missing: en.field_position set to 28
- Status changed from New to Can't reproduce
this code has been refactored a bit.
the messenger tests won't directly trigger this, though we may the/an underlying msgr bug that may have caused it. i don't think there's value in keeping this open.
- Tracker changed from Feature to Bug
- Status changed from Can't reproduce to New
- Tracker changed from Bug to Feature
- Subject changed from qa: messenger connect/reconnect tester to qa: spec out messenger testing
- Status changed from New to Resolved
we now have a high-level plan on how to attack msgr testing.
Also available in: Atom
PDF