On Thu, 2023-04-20 at 15:50 +0200, Simon Horman wrote: > On Thu, Apr 20, 2023 at 02:18:33PM +0200, David Marchand wrote: > > On Thu, Apr 20, 2023 at 2:06 PM Simon Horman <simon.hor...@corigine.com> > > wrote: > > > > I do see CI failures, but I think these are false negatives: > > > > > > > > * > > > > https://patchwork.ozlabs.org/project/openvswitch/patch/3f70ca7bafad296e18ed9579f30fd7044c47fc61.ca...@cloudandheat.com/ > > > > > > > > I'm retrying the GitHub based jobs here. > > > > > > > > * https://github.com/horms/ovs/actions/runs/4753793285 > > [1] > > > > The above succeeded, so I'm going to assume the previous failure > > > is unrelated to this patch. > > > > The bfd decay test is known to be flaky with ASan. > > > > Ilya had mentionned it initially when enabling ASan: > > https://mail.openvswitch.org/pipermail/ovs-dev/2021-February/380467.html > > More recently, Eelco mentionned it: > > https://mail.openvswitch.org/pipermail/ovs-dev/2022-September/397476.html > > I also see it every once in a while in GHA. > > Thanks. I've also observed that test is flakey. > > FWIIW, [1] passed, So I'm happy with this patch. > > Reviewed-by: Simon Horman <simon.hor...@corigine.com> >
Hi Simon, thanks for your review and reply. Do I need to take care of the intel-ovs-compilation pipeline? The test result looks good, but still some logs are written to the end, that I don't know, what to do with. https://mail.openvswitch.org/pipermail/ovs-build/2023-April/029983.html Otherwise, I would send a v2 of my patch without the stacktraces in the commit messages. _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
