iperf >2.0.13 blocks mininet 2.3.0 tests (e.g. in openvswitch autopkgtest)
Bug #1936796 reported by
Christian Ehrhardt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
iperf (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
mininet (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Hi,
this is the return of bug 1919432
Sadly upstream mininet did not continue on it https:/
Due to that we need to resolve it somehow or we will stay behind the new iperf for (too) long.
The details in the links above are long, but the TL;DR is:
- iperf changed the output in a few cases
- mininet needs to adapt in a way not loosing the ability to
wait for output
I'll try to apply my upstream suggestion if it lets the new iperf/openvsitch pass with valid results.
If it does I'll ask jamespage (for openvswitch experience) to have a look.
Related branches
~paelzer/ubuntu/+source/mininet:impish-lp-1936796
Merged
into
~paelzer/ubuntu/+source/mininet:master
at
revision 2c1ae8bbcfe459c67902995793ec5fc2061b3a86
- James Page (community): Approve
- Christian Ehrhardt : Approve
-
Diff: 60 lines (+40/-0)3 files modifieddebian/changelog (+12/-0)
debian/patches/fix-new-iperf.patch (+27/-0)
debian/patches/series (+1/-0)
tags: | added: update-excuse |
description: | updated |
Changed in iperf (Ubuntu): | |
status: | New → Confirmed |
Changed in mininet (Ubuntu): | |
status: | New → Triaged |
To post a comment you must log in.
After various tests in launchpad infrastructure I can confirm that my upstream suggested fix works (for us). /code.launchpad .net/~paelzer/ ubuntu/ +source/ mininet/ +git/mininet/ +merge/ 405896
Therfore I have nudged upstream again and prepared a merge proposal to fix the package.
=> https:/