On Fri, May 26, 2023 at 01:38:54PM +0200, Ales Musil wrote: > On Fri, May 26, 2023 at 12:56 PM Simon Horman <[email protected]> > wrote: > > > On Thu, May 25, 2023 at 12:23:43PM -0400, Brian Haley wrote: > > > Sorry for the top post, but I was wondering if there was a way to > > re-trigger > > > the bot testing action on a patch? Somehow the testing on the v2 one > > failed > > > even though v1 passed [0]. Since the only change was in the commit > > message > > > seems it could just be a flaky test? Unless I'm missing something. > > > > Hi Brian, > > > > I would suspect it is a flaky test too. Probably that should be addressed, > > for the reason that I think your email illustrates: it diminishes the value > > of the tests as a whole. > > > > As for your question. No, AFAIK, the tests can't be re-triggered. > > However, these tests are executed by GitHub actions. > > And if you push to a GitHub repository, say a copy of the > > OVN repository one that you control, then the tests will run. > > And you can also re-trigger them there. > > > > In this case the series_356692 branch of the ovsrobot/ovn repository > > would be of particular interest. > > > > Link: https://github.com/ovsrobot/ovn/actions/runs/5083467342 > > Hi, > > the test takes longer than the set timeout. I've posted a patch to extend > the timeout to the same value as ovn-kubernetes uses, this should hopefully > help.
Excellent, thanks Ales. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
