* [LTP] [PATCH v2 1/1] network/mc_cmds: fix testing with iproute2 <= ss161212
@ 2017-01-18 14:00 Petr Vorel
2017-01-19 17:30 ` Alexey Kodanev
2017-01-24 10:28 ` Cyril Hrubis
0 siblings, 2 replies; 5+ messages in thread
From: Petr Vorel @ 2017-01-18 14:00 UTC (permalink / raw)
To: ltp
Workaround for an upstream bug in ip:
https://bugzilla.kernel.org/show_bug.cgi?id=192741
+ add whitespace in log
Signed-off-by: Petr Vorel <pvorel@suse.cz>
---
* v1->v2: omit tail
---
testcases/network/multicast/mc_cmds/mc_cmds | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/testcases/network/multicast/mc_cmds/mc_cmds b/testcases/network/multicast/mc_cmds/mc_cmds
index 62f9e9197..cc6a8e39d 100755
--- a/testcases/network/multicast/mc_cmds/mc_cmds
+++ b/testcases/network/multicast/mc_cmds/mc_cmds
@@ -50,12 +50,16 @@ do_test()
ip addr show $(tst_iface) | grep -q 'MULTICAST' || \
tst_brkm TFAIL "Multicast not listed for $(tst_iface)"
- ip maddr show $(tst_iface) | grep -q '224.0.0.1' || \
- tst_brkm TFAIL "all-host-group for $(tst_iface) not joined"
+ ip maddr show $(tst_iface) | grep -q '224.0.0.1'
+ if [ $? -ne 0 ]; then
+ tst_resm TINFO "ip failed to detect multicast, parsing /proc/net/igmp"
+ grep "$(tst_iface)\s*:" -A 1 /proc/net/igmp | grep -q '\s010000E0\s' || \
+ tst_brkm TFAIL "all-host-group for $(tst_iface) not joined"
+ fi
# Do the ping tests: Execute ping 224.0.0.1 - Verify that the proper
# number of responses are returned.
- tst_resm TINFO "Ping all-host-groups address(over default route!)"
+ tst_resm TINFO "Ping all-host-groups address (over default route!)"
ping -c2 224.0.0.1 > ping_out.log || \
tst_brkm TFAIL "No response from MC hosts to ping 224.0.0.1"
--
2.11.0
^ permalink raw reply related [flat|nested] 5+ messages in thread
* [LTP] [PATCH v2 1/1] network/mc_cmds: fix testing with iproute2 <= ss161212
2017-01-18 14:00 [LTP] [PATCH v2 1/1] network/mc_cmds: fix testing with iproute2 <= ss161212 Petr Vorel
@ 2017-01-19 17:30 ` Alexey Kodanev
2017-01-24 10:28 ` Cyril Hrubis
1 sibling, 0 replies; 5+ messages in thread
From: Alexey Kodanev @ 2017-01-19 17:30 UTC (permalink / raw)
To: ltp
Hi Petr,
On 01/18/2017 05:00 PM, Petr Vorel wrote:
> Workaround for an upstream bug in ip:
> https://bugzilla.kernel.org/show_bug.cgi?id=192741
Applied, also added TWARN flag to tst_resm and reverted the change
with the missing white-space (in subsequent patch removed that section).
Thanks,
Alexey
^ permalink raw reply [flat|nested] 5+ messages in thread
* [LTP] [PATCH v2 1/1] network/mc_cmds: fix testing with iproute2 <= ss161212
2017-01-18 14:00 [LTP] [PATCH v2 1/1] network/mc_cmds: fix testing with iproute2 <= ss161212 Petr Vorel
2017-01-19 17:30 ` Alexey Kodanev
@ 2017-01-24 10:28 ` Cyril Hrubis
2017-01-24 12:06 ` Petr Vorel
1 sibling, 1 reply; 5+ messages in thread
From: Cyril Hrubis @ 2017-01-24 10:28 UTC (permalink / raw)
To: ltp
Hi!
> Workaround for an upstream bug in ip:
> https://bugzilla.kernel.org/show_bug.cgi?id=192741
I wonder if we should write a regression test for the ip as well. I
guess that some basic ip testsuite under testcases/commands/ wouldn't
hurt either.
--
Cyril Hrubis
chrubis@suse.cz
^ permalink raw reply [flat|nested] 5+ messages in thread
* [LTP] [PATCH v2 1/1] network/mc_cmds: fix testing with iproute2 <= ss161212
2017-01-24 10:28 ` Cyril Hrubis
@ 2017-01-24 12:06 ` Petr Vorel
2017-01-24 13:45 ` Cyril Hrubis
0 siblings, 1 reply; 5+ messages in thread
From: Petr Vorel @ 2017-01-24 12:06 UTC (permalink / raw)
To: ltp
Hi,
> > Workaround for an upstream bug in ip:
> > https://bugzilla.kernel.org/show_bug.cgi?id=192741
> I wonder if we should write a regression test for the ip as well. I
> guess that some basic ip testsuite under testcases/commands/ wouldn't
> hurt either.
I agree for the need of ip regression tests. If you don't mind I'd like to write this one.
Kind regards,
Petr
^ permalink raw reply [flat|nested] 5+ messages in thread
* [LTP] [PATCH v2 1/1] network/mc_cmds: fix testing with iproute2 <= ss161212
2017-01-24 12:06 ` Petr Vorel
@ 2017-01-24 13:45 ` Cyril Hrubis
0 siblings, 0 replies; 5+ messages in thread
From: Cyril Hrubis @ 2017-01-24 13:45 UTC (permalink / raw)
To: ltp
Hi!
> > I wonder if we should write a regression test for the ip as well. I
> > guess that some basic ip testsuite under testcases/commands/ wouldn't
> > hurt either.
>
> I agree for the need of ip regression tests. If you don't mind I'd like to write this one.
Go ahead :-)
--
Cyril Hrubis
chrubis@suse.cz
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2017-01-24 13:45 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-01-18 14:00 [LTP] [PATCH v2 1/1] network/mc_cmds: fix testing with iproute2 <= ss161212 Petr Vorel
2017-01-19 17:30 ` Alexey Kodanev
2017-01-24 10:28 ` Cyril Hrubis
2017-01-24 12:06 ` Petr Vorel
2017-01-24 13:45 ` Cyril Hrubis
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox