On Fri, May 24, 2019 at 07:26:47PM +0200, csfakian@redhat.com wrote:
From: Christos Sfakianakis csfakian@redhat.com
Allow 'msg_size' property of a Flow object to be set (to be used with ShortLivedConnectionsRecipe).
Signed-off-by: Christos Sfakianakis csfakian@redhat.com
lnst/RecipeCommon/Perf/Measurements/BaseFlowMeasurement.py | 4 ++++ 1 file changed, 4 insertions(+)
diff --git a/lnst/RecipeCommon/Perf/Measurements/BaseFlowMeasurement.py b/lnst/RecipeCommon/Perf/Measurements/BaseFlowMeasurement.py index c4448b7..81cd02c 100644 --- a/lnst/RecipeCommon/Perf/Measurements/BaseFlowMeasurement.py +++ b/lnst/RecipeCommon/Perf/Measurements/BaseFlowMeasurement.py @@ -46,6 +46,10 @@ class Flow(object): def msg_size(self): return self._msg_size
- @msg_size.setter
- def msg_size(self, value):
self._msg_size = value
- @property def duration(self): return self._duration
-- 2.17.1 _______________________________________________ LNST-developers mailing list -- lnst-developers@lists.fedorahosted.org To unsubscribe send an email to lnst-developers-leave@lists.fedorahosted.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/lnst-developers@lists.fedorahos...
Also not sure about this... I imagined that Flow instances shouldn't really be changed once they're created. I'll take a look at the use case but I think it's probably a better idea to not reuse Flow instances and just create a new one when needed.
-Ondrej