All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 757] fast-tests failures in an Ubuntu autopkgtest environment hash_autotest, per_lcore_autotest, rcu_qsbr_autotest, table_autotest
Date: Fri, 16 Jul 2021 07:04:48 +0000	[thread overview]
Message-ID: <bug-757-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 757
           Summary: fast-tests failures in an Ubuntu autopkgtest
                    environment hash_autotest, per_lcore_autotest,
                    rcu_qsbr_autotest, table_autotest
           Product: DPDK
           Version: 20.11
          Hardware: All
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: christian.ehrhardt@canonical.com
  Target Milestone: ---

Hi,
as part of the CI we are running the fast-tests after every build in Debian and
Ubuntu [1][2][3]. As part of this we happened to see that in this environment
some issues occur.

This issue is about 4 tests which fail reliably in the Ubuntu autopkgtest
environment.

15/58 DPDK:fast-tests / hash_autotest            FAIL           0.47s (killed
by signal 6 SIGABRT)
22/58 DPDK:fast-tests / per_lcore_autotest       FAIL           0.22s (exit
status 255 or signal 127 SIGinvalid)
24/58 DPDK:fast-tests / rcu_qsbr_autotest        FAIL           0.33s (killed
by signal 6 SIGABRT)
36/58 DPDK:fast-tests / table_autotest           FAIL           1.21s (killed
by signal 9 SIGKILL)

Detailed logs are at [4][5][6].
Interstingly the very same tests in a rather similar environment in Dbeian do
not fail [7][8][9].
The difference might be the used compiler/toolchain versions and defaults.

[1]: https://packaging.ubuntu.com/html/auto-pkg-test.html
[2]: https://autopkgtest.ubuntu.com/
[3]: https://ci.debian.net/
[4]:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/d/dpdk/20210712_095836_75b36@/log.gz
[5]:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/d/dpdk/20210712_100606_75b36@/log.gz
[6]:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/d/dpdk/20210712_100428_a7086@/log.gz
[7]:
https://ci.debian.net/data/autopkgtest/unstable/ppc64el/d/dpdk/13543407/log.gz
[8]:
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dpdk/13543196/log.gz
[9]:
https://ci.debian.net/data/autopkgtest/unstable/arm64/d/dpdk/13543256/log.gz

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

                 reply	other threads:[~2021-07-16  7:04 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-757-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.