On Fri, May 26, 2023 at 01:38:54PM +0200, Ales Musil wrote:
> On Fri, May 26, 2023 at 12:56 PM Simon Horman
> 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 acti
On Fri, May 26, 2023 at 12:56 PM Simon Horman
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
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
> se
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.
DNS queries with optional records (RRs), for example, with
cookies for EDNS, are not supported by the OVN resolver.
Trying to reply sometimes results in mangled responses
that clients do not understand.
Instead, just return early when one is present, which
should trigger a negative response and ca
