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
wrote:
> On Tue, Apr 2, 2024 at 2:46 AM Stephen Hemminger
> wrote:
> >
> > On Mon, 1 Apr 2024 18:26:44 -0400
> > Patrick Rob
On Tue, Apr 2, 2024 at 2:46 AM Stephen Hemminger
wrote:
>
> On Mon, 1 Apr 2024 18:26:44 -0400
> Patrick Robb 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 redu
On Mon, 1 Apr 2024 18:26:44 -0400
Patrick Robb 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 issu
On Fri, Mar 22, 2024 at 7:34 PM Stephen Hemminger
wrote:
>
>
> Could you build a simple test to see if TSC every runs backwards on
> this machine. Or there could be yet another math error.
> Or maybe container TSC is huge an wrapping around?
>
> The point of the test is to make sure that there was
On Fri, 22 Mar 2024 13:12:24 -0400
Patrick Robb wrote:
> Hi David,
>
> Yes I'm seeing this pcapng_autotest fail intermittently on debian 11
> recently. It also got flagged on Slack, where Stephen indicated it is
> likely a lab infra failure.
>
> Anyways, I guess based on the logs above it is a
Hi David,
Yes I'm seeing this pcapng_autotest fail intermittently on debian 11
recently. It also got flagged on Slack, where Stephen indicated it is
likely a lab infra failure.
Anyways, I guess based on the logs above it is a timestamp error from
TSC (as you can see HPET is not used). Indeed, the
Hello Stephen,
I noticed a (time based?) failure of the pcapng unit test in some UNH
Debian 11 container.
Please have a look.
https://lab.dpdk.org/results/dashboard/patchsets/29604/
--- stdout ---
RTE>>pcapng_autotest
+ ---
7 matches
Mail list logo
