On Tue, Sep 30, 2014 at 5:13 PM, Joe Stringer
wrote:
> Maybe just stick with 5.
>
>
5 it is,
also fold in the following check, applied to master~
diff --git a/tests/ovs-vswitchd.at b/tests/ovs-vswitchd.at
index 9be3078..2c72a7f 100644
--- a/tests/ovs-vswitchd.at
+++ b/tests/ovs-vswitchd.at
@@ -
Maybe just stick with 5.
On 1 October 2014 13:10, Alex Wang wrote:
> Yeah, so should we use 5 seconds? or use ovs_wait() to wait on the number
> of lines which could wait up to 10 seconds...?
>
> On Tue, Sep 30, 2014 at 4:14 PM, Joe Stringer
> wrote:
>
>> I had a play around and could only rep
Yeah, so should we use 5 seconds? or use ovs_wait() to wait on the number
of lines which could wait up to 10 seconds...?
On Tue, Sep 30, 2014 at 4:14 PM, Joe Stringer
wrote:
> I had a play around and could only reproduce the bug with mininum 3
> seconds.
>
>
> On 1 October 2014 12:11, Alex Wang
I had a play around and could only reproduce the bug with mininum 3 seconds.
On 1 October 2014 12:11, Alex Wang wrote:
> Thx for the review~
>
> 5 seems high, is this just to make sure that vswitchd gets a chance to
>> fully initialize and go through the wait block once?
>>
>
> Yeah, also to may
Thx for the review~
5 seems high, is this just to make sure that vswitchd gets a chance to
> fully initialize and go through the wait block once?
>
Yeah, also to maybe cumulate more logs, if there is something.
How about changing it to 2 s?
> Acked-by: Joe Stringer
>
Awesome, thanks for the fix.
On 1 October 2014 10:01, Alex Wang wrote:
>
> +dnl --
+AT_SETUP([ovs-vswitchd -- start additional ovs-vswitchd process])
+OVS_VSWITCHD_START
+
+# start another ovs-vswitchd process.
+ovs-vswitchd --l
When there are more than one ovs-vswitchd processes started,
only one process is enabled. The disabled processes should
just sleep. However, a bug in ovs makes the disabled processes
keep waking up on global connectivity sequence number which is
never sync'ed. Consequently, those processes use 1
