From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: honnappa.nagarahalli@arm.com, robot@bytheb.org
Subject: |FAILURE| pw124885 [PATCH 4/4] mempool: use lcore API to check if lcore ID is valid
Date: Thu, 9 Mar 2023 02:39:24 -0500 [thread overview]
Message-ID: <20230309073924.244468-1-robot@bytheb.org> (raw)
In-Reply-To: <20230309045738.1261000-5-honnappa.nagarahalli@arm.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/124885/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4371358748
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-abi+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-abi+doc+tests" at step Build and test
####################################################################################
95/104 DPDK:fast-tests / telemetry_data_autotest OK 0.17 s
96/104 DPDK:fast-tests / table_autotest OK 6.33 s
97/104 DPDK:fast-tests / ring_pmd_autotest OK 0.17 s
98/104 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 0.62 s
99/104 DPDK:fast-tests / bitratestats_autotest OK 0.17 s
100/104 DPDK:fast-tests / latencystats_autotest OK 0.17 s
101/104 DPDK:fast-tests / pdump_autotest FAIL 0.17 s (killed by signal 11 SIGSEGV)
102/104 DPDK:fast-tests / vdev_autotest OK 0.17 s
103/104 DPDK:fast-tests / compressdev_autotest SKIP 0.17 s
104/104 DPDK:fast-tests / telemetry_all OK 8.93 s
Ok: 95
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 8
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-abi+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2023-03-09 6:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230309045738.1261000-5-honnappa.nagarahalli@arm.com>
2023-03-09 4:48 ` |SUCCESS| pw124882-124885 " qemudev
2023-03-09 4:51 ` |FAILURE| " qemudev
2023-03-09 4:58 ` |WARNING| pw124885 " checkpatch
2023-03-09 7:39 ` 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=20230309073924.244468-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=honnappa.nagarahalli@arm.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).