On Thu, Apr 06, 2023 at 05:25:06PM +0200, Dumitru Ceara wrote:
> On 4/6/23 14:45, Simon Horman wrote:
> > On Thu, Apr 06, 2023 at 02:07:00PM +0200, Dumitru Ceara wrote:
> >> On 4/5/23 14:43, Simon Horman wrote:
> >>> On Tue, Apr 04, 2023 at 11:01:26PM +0200, Lorenzo Bianconi wrote:
> >>>> Similar to qos_max_rate and qos_burst, take into account qos_min_rate in
> >>>> port_has_qos_params routine.
> >>>>
> >>>> Fixes: dbf12e5fe1f7 ("qos: add support for port minimum bandwidth 
> >>>> guarantee")
> >>>> Signed-off-by: Lorenzo Bianconi <[email protected]>
> >>>
> >>> Hi Lorenzo,
> >>>
> >>
> >> Hi Simon,
> >>
> >>> I am unsure if it is related to this change, or perhaps a transient error,
> >>> but the ovn-kubernetes workflow run failed when run against this patch.
> >>>
> >>> https://patchwork.ozlabs.org/project/ovn/patch/48d88894b808e03bbcc513b8793bc92d85eea657.1680642050.git.lorenzo.bianc...@redhat.com/
> >>>
> >>
> >> Sorry, I missed your message here and already applied the patch.  I'm
> >> quite confident it's unrelated though.
> > 
> > No problem. I also feel it is likely to be unrelated.
> > 
> >>> FWIIW, I am experimenting with re-running the workflow here:
> >>>
> >>> https://github.com/horms/ovn/actions/runs/4618557664
> >>>
> >>
> >> Let's see how the ovn-org/ovn jobs fare too:
> >>
> >> https://github.com/ovn-org/ovn/actions/workflows/ovn-kubernetes.yml
> > 
> > Yes, good idea.
> > 
> 
> This actually uncovered a regression in ovn-kubernetes. :)

Seems that the workflow is helping us :)
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to