From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2F81843D28; Sat, 23 Mar 2024 00:34:35 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8107042FE7; Sat, 23 Mar 2024 00:34:34 +0100 (CET) Received: from mail-pj1-f46.google.com (mail-pj1-f46.google.com [209.85.216.46]) by mails.dpdk.org (Postfix) with ESMTP id 50C6B402BD for ; Sat, 23 Mar 2024 00:34:33 +0100 (CET) Received: by mail-pj1-f46.google.com with SMTP id 98e67ed59e1d1-29a8911d11cso1579921a91.1 for ; Fri, 22 Mar 2024 16:34:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1711150472; x=1711755272; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=ivPSTCBiAd/NRS3sBok+tYOCUFu1Rg72l88AkSv5APU=; b=Yn+uB5EawddWTLFwSVZT8jNmVQRInOwJT5bvdGlgJlRTgZfDWXryCFmA9/CPvxJ5gP Fz65FQvMNhXLSehGxl6pD2eptW50f0TeDsP0OCK6Aj033IgKiY7rmldsyplj7YOdws9v OC3qKMzKa78LZ+pXC5zK0kVKjbNIxqUX2AYpENfoAJoMPQbwSqrFGW19yhGR+h72kJiJ Shr4x4AekcVH0R4D+YfHdc8i0ECAGEYTh/ZaOS9gSJABeTU1JLZ7jco8KawrjM89mzIA uCzvU4kfPjHxM1RlWjTvegNVYSOv/kTo3Q9dgZijE7xWyZkc+498hKyp8JcNyfxeLjwZ bGmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711150472; x=1711755272; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ivPSTCBiAd/NRS3sBok+tYOCUFu1Rg72l88AkSv5APU=; b=RPA2kBxYuUODSV48UvWhRTf2WfgccXmuw2dI/0h9b8SUxIJSEFsBZ0sdRF5yJOgtQl QNYM60op14EH8+gqzFObVagO7na4BU0V7CDEUbMYannvu8BBnuVIgN2EY0WXb60fcqIs OAuy9PhE4Bif0JrjHoYNubc/cINrJ8lazMsNlBvSI9TWO2raxRBr7G+MmZqNjlvOVMu+ 0ZRLwAk1H3tV7cwc2dHAW3p7fdv5k0XbfQNNgHLvADQI9Q3kR/k99FBNGSQlCA2eLY5F Dt2Ihg/ZPA6CrikfOIpl3qBQV6viG+yXxWGiPVkmQ6ArntSN5a2bUXrwWAKu6QdTEG9O ALLg== X-Forwarded-Encrypted: i=1; AJvYcCXJGYo1+G1tHQhXl7UOj2rbe0GDd71+GyQQ4NZ3axtYFbLQqQnl9eg7idDEAwR2T8RxieYIkF4Bkgg6J1g= X-Gm-Message-State: AOJu0Yz4hOduQaoG6nQ5CbZvG6K8pftG/4PXsQY8wyL+MNBMpy5eLRcw GCxRRrksrSUkvEqh7il4/mxbyNwDkqxAtGfTOyOgcMQu3IpjfFUsqYIc4r9pMMo= X-Google-Smtp-Source: AGHT+IEs+NhhlvbqFI+5q4iK1yeBCu/5/UV96CXDzaEAKR2x6uJRnjT9TWB3nQD0fSCsAW0vbJvK6g== X-Received: by 2002:a17:90a:d710:b0:29c:7592:febf with SMTP id y16-20020a17090ad71000b0029c7592febfmr985141pju.16.1711150472194; Fri, 22 Mar 2024 16:34:32 -0700 (PDT) Received: from hermes.local (204-195-123-203.wavecable.com. [204.195.123.203]) by smtp.gmail.com with ESMTPSA id kx16-20020a17090b229000b0029b77fbeb7fsm6158312pjb.16.2024.03.22.16.34.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Mar 2024 16:34:32 -0700 (PDT) Date: Fri, 22 Mar 2024 16:34:30 -0700 From: Stephen Hemminger To: Patrick Robb Cc: David Marchand , dev , Aaron Conole , ci@dpdk.org, Cody Cheng Subject: Re: pcapng_autotest unit test false positive Message-ID: <20240322163430.444bed0c@hermes.local> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Fri, 22 Mar 2024 13:12:24 -0400 Patrick Robb wrote: > Hi David, >=20 > 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. >=20 > 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 write_packets test > that is failing does call rte_get_tsc_cycles(). >=20 > So, some steps I think we should take. >=20 > 1. Refresh the debian11 test container image we are using in CI testing. > 2. Reset VM which containers are running on (which does also reset tsc > cycle counter of course). > 3. Re-image our VMs which the test containers run on, bringing it to > Ubuntu 22.04 and a newer kernel version. >=20 > If that fails, I guess we can also look at substituting HPET for TSC. > It looks like (provided you have set the right bootloader option) you > use -Duse_hpet=3Dtrue with meson for this. But, it looks like the unit > test is written to use TSC instead of HPET anyways, so I don't think > this is relevant. >=20 > Does this sound reasonable? If so we will proceed. >=20 > @Cody Cheng Since I know you are refreshing the lab container images > anyways, let's bring debian 11 to the front of the queue. Thanks. >=20 > On Wed, Mar 20, 2024 at 2:02=E2=80=AFPM David Marchand > wrote: > > > > 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 ----------------------------= ------- =20 > > RTE>>pcapng_autotest =20 > > + ------------------------------------------------------- + > > + Test Suite : Test Pcapng Unit Test Suite > > + ------------------------------------------------------- + > > pcapng: output file /tmp/pcapng_test_oIueHb.pcapng > > + TestCase [ 0] : test_add_interface succeeded > > pcapng: output file /tmp/pcapng_test_4hbuWV.pcapng > > 16:51:22.955616600: EE:47:6C:93:DE:F0 -> FF:FF:FF:FF:FF:FF type 800 len= gth 200 > > + TestCase [ 1] : test_write_packets failed > > + ------------------------------------------------------- + > > + Test Suite Summary : Test Pcapng Unit Test Suite > > + ------------------------------------------------------- + > > + Tests Total : 2 > > + Tests Skipped : 0 > > + Tests Executed : 2 > > + Tests Unsupported: 0 > > + Tests Passed : 1 > > + Tests Failed : 1 > > + ------------------------------------------------------- + > > Test Failed =20 > > RTE>> =20 > > ----------------------------------- stderr ----------------------------= ------- > > EAL: Detected CPU lcores: 16 > > EAL: Detected NUMA nodes: 2 > > EAL: Detected static linkage of DPDK > > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket > > EAL: Selected IOVA mode 'VA' > > EAL: VFIO support initialized > > EAL: Device 0000:03:00.0 is not NUMA-aware > > APP: HPET is not enabled, using TSC as default timer > > Timestamp out of range [16:51:16.481074161 .. 16:51:22.953203736] > > pcap_dispatch: failed: > > > > > > -- > > David Marchand > > =20 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 wasn't wraparound errors.