From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: lizh@nvidia.com, robot@bytheb.org
Subject: |FAILURE| pw112391 [PATCH v1 17/17] vdpa/mlx5: prepare virtqueue resource creation
Date: Mon, 6 Jun 2022 08:40:55 -0400 [thread overview]
Message-ID: <20220606124055.28413-1-robot@bytheb.org> (raw)
In-Reply-To: <20220606114650.209612-18-lizh@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/112391/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/2447580027
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-shared-abi+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-shared-abi+doc+tests" at step Build and test
####################################################################################
91/100 DPDK:fast-tests / telemetry_json_autotest OK 0.17 s
92/100 DPDK:fast-tests / telemetry_data_autotest OK 0.17 s
93/100 DPDK:fast-tests / table_autotest OK 9.35 s
94/100 DPDK:fast-tests / ring_pmd_autotest OK 0.17 s
95/100 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 0.87 s
96/100 DPDK:fast-tests / bitratestats_autotest OK 0.17 s
97/100 DPDK:fast-tests / latencystats_autotest OK 0.17 s
98/100 DPDK:fast-tests / pdump_autotest FAIL 5.29 s (killed by signal 11 SIGSEGV)
99/100 DPDK:fast-tests / vdev_autotest OK 0.17 s
100/100 DPDK:fast-tests / compressdev_autotest SKIP 0.17 s
Ok: 93
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 6
Timeout: 0
Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-shared-abi+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2022-06-06 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220606114650.209612-18-lizh@nvidia.com>
2022-06-06 11:50 ` |SUCCESS| " checkpatch
2022-06-06 12:40 ` 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=20220606124055.28413-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=lizh@nvidia.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).