From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: david.marchand@redhat.com, robot@bytheb.org
Subject: [dpdk-test-report] |FAILURE| pw91596 [dpdk-dev] [PATCH] ci: bump ABI reference version
Date: Thu, 15 Apr 2021 13:57:03 -0400 [thread overview]
Message-ID: <20210415175703.24643-1-robot@bytheb.org> (raw)
In-Reply-To: <20210415163230.22263-1-david.marchand@redhat.com>
From: robot@bytheb.org
Test-Label: github-robot
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/91596/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/752805922
Build Logs:
-----------------------Summary of failed steps-----------------------
ubuntu-18.04-gcc-shared-abi+doc+tests failed at step "Build and test"
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] ubuntu-18.04-gcc-shared-abi+doc+tests at step "Build and test"
####################################################################################
Native dependency libpcap found: YES 1.8.1
Has header "pcap.h": YES
Compiler for C supports arguments -Wextra: YES
Compiler for C supports arguments -Wcast-qual: YES
Compiler for C supports arguments -Wdeprecated: YES
Compiler for C supports arguments -Wformat: YES
Compiler for C supports arguments -Wformat-nonliteral: YES
Compiler for C supports arguments -Wformat-security: YES
Compiler for C supports arguments -Wmissing-declarations: YES
Compiler for C supports arguments -Wmissing-prototypes: YES
Compiler for C supports arguments -Wnested-externs: YES
Compiler for C supports arguments -Wold-style-definition: YES
Compiler for C supports arguments -Wpointer-arith: YES
Compiler for C supports arguments -Wsign-compare: YES
Compiler for C supports arguments -Wstrict-prototypes: YES
Compiler for C supports arguments -Wundef: YES
Compiler for C supports arguments -Wwrite-strings: YES
Compiler for C supports arguments -Wno-address-of-packed-member -Waddress-of-packed-member: NO
Compiler for C supports arguments -Wno-packed-not-aligned -Wpacked-not-aligned: NO
Compiler for C supports arguments -Wno-missing-field-initializers -Wmissing-field-initializers: YES
config/x86/meson.build:14:6: ERROR: Could not get define '__SSE4_2__'
A full log can be found at /home/runner/work/dpdk/dpdk-v21.02/build/meson-logs/meson-log.txt
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] ubuntu-18.04-gcc-shared-abi+doc+tests at step "Build and test"
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2021-04-15 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210415163230.22263-1-david.marchand@redhat.com>
2021-04-15 16:33 ` [dpdk-test-report] |WARNING| pw91596 " checkpatch
2021-04-15 17:55 ` [dpdk-test-report] |FAILURE| pw91596 " 0-day Robot
2021-04-15 17:57 ` 0-day Robot [this message]
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=20210415175703.24643-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=david.marchand@redhat.com \
--cc=test-report@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 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).