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 3EE3A43D24; Fri, 22 Mar 2024 18:12:36 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2AE7640294; Fri, 22 Mar 2024 18:12:36 +0100 (CET) Received: from mail-oi1-f169.google.com (mail-oi1-f169.google.com [209.85.167.169]) by mails.dpdk.org (Postfix) with ESMTP id 6DB2B40284 for ; Fri, 22 Mar 2024 18:12:35 +0100 (CET) Received: by mail-oi1-f169.google.com with SMTP id 5614622812f47-3c3a4101721so1454272b6e.1 for ; Fri, 22 Mar 2024 10:12:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1711127554; x=1711732354; darn=dpdk.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=iThSbit1H5CF4bUX6wfbYPkyDBg+PstV5NE9lpwPBZg=; b=fqf9igxuTPVGsPBcKxxADkabyPwhIEOxX/R02ar9x5HK0aWyd4XcVwt+eMtbWKNY5/ NK4SdrWwMigD8PjKLpHFFSC9j3khPQ8CVLvTS6rFKeWZuohN/zSQBVWpmSMgTFCCwxnD aCg4nkAfS2stD0mPh1VrEJKyhveMCDz9Qz12k= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711127554; x=1711732354; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=iThSbit1H5CF4bUX6wfbYPkyDBg+PstV5NE9lpwPBZg=; b=nW4pr7/wx5aRsQCxmrf0Vk+QnoZpVjvHlcCBUzkMlebyjM06xfkngGTb2y7seqLWaS Org2IgZGmovQFEigGKiXY4dWpxLVBHaJzT2RepFWKbeTTv13yY08SQl8xRYeQzvq0A/M zcd2ifg444z5bnRUcNmeS4aeD83/BHLxgBUtWRz0BtWR5k2ANg+dxiGMSrhIEi0/W7X2 DOo8m7ldQE2Un9ynKl4nOoC1L5wx30qbqxy8gdsR35ToNAj9Xhr9Uix83ddvDROsdaGc n3MVqOgzG/CMyW3SqrXxypy5aT8ZdMnjbOZEeRPTp9hCyjHq5owGmuDxe7TfCG7NuFMI bgbA== X-Forwarded-Encrypted: i=1; AJvYcCUNgdbv8e+U5VGHn6VhicggW3s93GZ81qS++5kcqGkVL50bO5KhCpoHiHAzAipKLS9gd4x9rMuzx5YqINY= X-Gm-Message-State: AOJu0YwTEm5hc8Rad+RiPETJVkfsLVPQDP0UmsV7tLLlMXN4CxCiYoT0 ufzbwbD5627WnywBzM6gqpxHG7QODZSq+BGRQf0o8ZwUEkuGGKldWdVoyxmMC9EbYPeKqpP7OhC L8xRFSFmvNU9cAMAdGJswOvOVY4mTbDct18XF7A== X-Google-Smtp-Source: AGHT+IEqljxywJbYcerUYb+Sx1bsEzLo0fUTxCq9lSv6SPEGfuPQoelG6bIQYkXakGKHSZibyFuKjL1bKCQr4qB2fBY= X-Received: by 2002:a05:6808:1490:b0:3c3:c0a1:6a81 with SMTP id e16-20020a056808149000b003c3c0a16a81mr217789oiw.6.1711127554803; Fri, 22 Mar 2024 10:12:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Patrick Robb Date: Fri, 22 Mar 2024 13:12:24 -0400 Message-ID: Subject: Re: pcapng_autotest unit test false positive To: David Marchand Cc: Stephen Hemminger , dev , Aaron Conole , ci@dpdk.org, Cody Cheng 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 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 write_packets test that is failing does call rte_get_tsc_cycles(). So, some steps I think we should take. 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. 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. Does this sound reasonable? If so we will proceed. @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. 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 ------------------------------= ----- > RTE>>pcapng_autotest > + ------------------------------------------------------- + > + 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 lengt= h 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 > RTE>> > ----------------------------------- 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 >