DPDK CI discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Harry van Haaren <harry.van.haaren@intel.com>
Cc: dev@dpdk.org, dpdklab@iol.unh.edu, ci@dpdk.org,
	Honnappa.Nagarahalli@arm.com, mattias.ronnblom@ericsson.com,
	thomas@monjalon.net, "Morten Brørup" <mb@smartsharesystems.com>,
	"Tyler Retzlaff" <roretzla@linux.microsoft.com>,
	"Aaron Conole" <aconole@redhat.com>
Subject: Re: [PATCH v3] test/service: fix spurious failures by extending timeout
Date: Thu, 26 Jan 2023 10:29:52 +0100	[thread overview]
Message-ID: <CAJFAV8woA7ET1Hb0zzyaMP-YvoRbjU15jJ8Yu9zB3dH9bnDH8Q@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8xL9wYC3ij9ut5A8GDd8_a5cMzkPzw9TNhnhUF229n-ng@mail.gmail.com>

Hello Harry,

On Thu, Oct 6, 2022 at 9:33 PM David Marchand <david.marchand@redhat.com> wrote:
>
> On Thu, Oct 6, 2022 at 3:27 PM Morten Brørup <mb@smartsharesystems.com> wrote:
> > > This commit extends the timeout for service_may_be_active()
> > > from 100ms to 1000ms. Local testing on a idle and loaded system
> > > (compiling DPDK with all cores) always completes after 1 ms.
> > >
> > > The wait time for a service-lcore to finish is also extended
> > > from 100ms to 1000ms.
> > >
> > > The same timeout waiting code was duplicated in two tests, and
> > > is now refactored to a standalone function avoiding duplication.
> > >
> > > Reported-by: David Marchand <david.marchand@redhat.com>
> > > Suggested-by: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
> > > Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
> > Acked-by: Morten Brørup <mb@smartsharesystems.com>
> Reviewed-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
>
> Ok, let's see if the situation gets better with this.
> Applied, thanks.

I took a look at the january month failures at UNH.

Downloads/dpdk_31608e4db568_2023-01-03_06-58-00_NA/out/testlog.txt:EAL:
Test assert service_lcore_attr_get line 422 failed: Service lcore not
stopped after waiting.
Extending the timeout just made it less likely.

On a similar note, other parts are failing every once in a while:
Downloads/dpdk_2a211079a92e_25064_2023-01-24_15-08-50_NA/out/testlog.txt:EAL:
Test assert service_attr_get line 319 failed: attr_get() failed to get
cycles (expected > zero)
Downloads/dpdk_2a211079a92e_25074_2023-01-25_05-40-46_NA/out/testlog.txt:EAL:
Test assert service_lcore_start_stop line 900 failed: Service core
expected to poll service but it didn't
Downloads/dpdk_2a211079a92e_25075_2023-01-25_09-15-58_NA/out/testlog.txt:EAL:
Test assert service_lcore_start_stop line 900 failed: Service core
expected to poll service but it didn't
Downloads/dpdk_373f4c7de8ff_24866_2023-01-03_22-56-01_NA/out/testlog.txt:EAL:
Test assert service_lcore_start_stop line 900 failed: Service core
expected to poll service but it didn't
Downloads/dpdk_83397b9f0739_25030_2023-01-18_18-30-19_NA/out/testlog.txt:EAL:
Test assert service_lcore_start_stop line 901 failed: Service core
expected to poll service but it didn't

The timeout approach just does not have its place in a functional test.
Either this test is rewritten, or it must go to the performance tests
list so that we stop getting false positives.

Can you work on this?


Thanks.

-- 
David Marchand


  reply	other threads:[~2023-01-26  9:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06  8:17 [PATCH] " Harry van Haaren
2022-10-06  8:28 ` [PATCH v2] " Harry van Haaren
2022-10-06  8:39   ` David Marchand
2022-10-06  8:54     ` Mattias Rönnblom
2022-10-06  8:37 ` [PATCH] " Mattias Rönnblom
2022-10-06 12:52 ` [PATCH v3] " Harry van Haaren
2022-10-06 13:27   ` Morten Brørup
2022-10-06 19:33     ` David Marchand
2023-01-26  9:29       ` David Marchand [this message]
2023-01-31 17:24         ` Van Haaren, Harry
2023-02-03 15:03           ` Van Haaren, Harry
2023-02-03 15:12             ` Bruce Richardson
2023-02-23 20:10               ` Thomas Monjalon
2023-02-27  8:41                 ` Van Haaren, Harry
2023-02-03 15:16             ` Thomas Monjalon
2023-02-03 16:09               ` Van Haaren, Harry
2023-02-23 20:15                 ` Thomas Monjalon
2023-02-27  8:41                   ` Van Haaren, Harry
2022-10-06 14:00   ` Mattias Rönnblom

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=CAJFAV8woA7ET1Hb0zzyaMP-YvoRbjU15jJ8Yu9zB3dH9bnDH8Q@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=harry.van.haaren@intel.com \
    --cc=mattias.ronnblom@ericsson.com \
    --cc=mb@smartsharesystems.com \
    --cc=roretzla@linux.microsoft.com \
    --cc=thomas@monjalon.net \
    /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).