All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1176] errno_autotest failing with musl
Date: Fri, 10 Mar 2023 09:54:32 +0000	[thread overview]
Message-ID: <bug-1176-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]

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

            Bug ID: 1176
           Summary: errno_autotest failing with musl
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: david.marchand@redhat.com
  Target Milestone: ---

On Alpine linux, the errno unit test fails with:

14/70 DPDK:fast-tests / errno_autotest        FAIL     0.22 s (exit status 255
or signal 127 SIGinvalid)

--- command ---
08:30:31 DPDK_TEST='errno_autotest' /__w/dpdk/dpdk/build/app/test/dpdk-test
--no-huge -m 2048 --file-prefix=errno_autotest
--- stdout ---
RTE>>errno_autotest
rte_strerror: 'Resource temporarily unavailable', strerror: 'Resource
temporarily unavailable'
rte_strerror: 'Bad file descriptor', strerror: 'Bad file descriptor'
rte_strerror: 'Permission denied', strerror: 'Permission denied'
rte_strerror: 'Interrupted system call', strerror: 'Interrupted system call'
rte_strerror: 'Invalid argument', strerror: 'Invalid argument'
rte_strerror: 'Invalid call in secondary process', strerror: 'No error
information'
Error, duplicate error code 1001
Test Failed

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

[-- Attachment #2: Type: text/html, Size: 3250 bytes --]

                 reply	other threads:[~2023-03-10  9:54 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-1176-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.