All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 341] repeated execution of distributor_autotest fails
Date: Mon, 19 Aug 2019 14:38:28 +0000	[thread overview]
Message-ID: <bug-341-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=341

            Bug ID: 341
           Summary: repeated execution of distributor_autotest fails
           Product: DPDK
           Version: 19.08
          Hardware: All
                OS: Linux
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: hkalra@marvell.com
  Target Milestone: ---

Created attachment 67
  --> https://bugs.dpdk.org/attachment.cgi?id=67&action=edit
Logs of the error message

Repeated execution of "distributor_autotest" test command fails with the
following error message:
=== testing big burst (burst) ===
Error: could not find source packet #1009


Steps to reproduce:
1. ./build/app/test -c f
2. execute "distributor_autotest"
3. First time it will execute successfully
4. again execute "distributor_autotest"

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2019-08-19 14:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-341-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.