From: Patrick Robb <probb@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
dev <dev@dpdk.org>, Aaron Conole <aconole@redhat.com>,
ci@dpdk.org, Cody Cheng <ccheng@iol.unh.edu>
Subject: Re: pcapng_autotest unit test false positive
Date: Thu, 15 May 2025 14:33:05 +0200 [thread overview]
Message-ID: <CAJvnSUCXns=JXV0FsWENqsifNzCA2NQhqJBCwDsfh=S4BbWy2A@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8xyZnjXVdbi3hsiSKMN5200H6tymEpxZ3O38X-Mh_dsFQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
Okay, I'll make a ticket for us to look at this again and raise it at the
CI meeting this morning. Thanks for the heads up.
On Thu, May 15, 2025 at 8:59 AM David Marchand <david.marchand@redhat.com>
wrote:
> On Tue, Apr 2, 2024 at 2:46 AM Stephen Hemminger
> <stephen@networkplumber.org> wrote:
> >
> > On Mon, 1 Apr 2024 18:26:44 -0400
> > Patrick Robb <probb@iol.unh.edu> wrote:
> >
> > > Another idea - maybe multiple timestamps are gathered from different
> > > CPU registers during the same test, and they are misaligned for that
> > > reason. Maybe we can try reducing the cores for each unit test to 1
> > > and checking whether the issue persists.
> >
> > TSC is expected to be sync'd between cores. But of course packets can
> > arrive out of order on different cores.
>
> Just a note that there was one more occurence of this false positive today.
> https://lab.dpdk.org/results/dashboard/patchsets/33170/
>
>
> --
> David Marchand
>
>
[-- Attachment #2: Type: text/html, Size: 1612 bytes --]
prev parent reply other threads:[~2025-05-15 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 18:02 David Marchand
2024-03-22 17:12 ` Patrick Robb
2024-03-22 23:34 ` Stephen Hemminger
2024-04-01 22:26 ` Patrick Robb
2024-04-02 0:46 ` Stephen Hemminger
2025-05-15 6:59 ` David Marchand
2025-05-15 12:33 ` Patrick Robb [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJvnSUCXns=JXV0FsWENqsifNzCA2NQhqJBCwDsfh=S4BbWy2A@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=ccheng@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).