From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: changfengnan@bytedance.com, robot@bytheb.org
Subject: |FAILURE| pw127162 [PATCH v2] eal: fix eal init may failed when too much continuous memsegs under legacy mode
Date: Mon, 22 May 2023 11:40:11 -0400 [thread overview]
Message-ID: <20230522154011.85691-1-robot@bytheb.org> (raw)
In-Reply-To: <20230522124107.99877-1-changfengnan@bytedance.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/127162/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/5047435268
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-abi+debug+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-abi+debug+doc+tests" at step Build and test
####################################################################################
96/105 DPDK:fast-tests / table_autotest OK 17.14 s
97/105 DPDK:fast-tests / ring_pmd_autotest OK 0.17 s
98/105 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.37 s
99/105 DPDK:fast-tests / bitratestats_autotest OK 0.17 s
100/105 DPDK:fast-tests / latencystats_autotest OK 0.17 s
101/105 DPDK:fast-tests / pdump_autotest OK 5.24 s
102/105 DPDK:fast-tests / vdev_autotest OK 0.17 s
103/105 DPDK:fast-tests / rawdev_autotest OK 0.17 s
104/105 DPDK:fast-tests / compressdev_autotest SKIP 0.17 s
105/105 DPDK:fast-tests / telemetry_all OK 9.40 s
Ok: 96
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+debug+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2023-05-22 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230522124107.99877-1-changfengnan@bytedance.com>
2023-05-22 12:41 ` |WARNING| " checkpatch
2023-05-22 15:40 ` 0-day Robot [this message]
2023-05-23 11:19 ` |SUCCESS| " qemudev
2023-05-23 11:20 ` |FAILURE| " qemudev
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=20230522154011.85691-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=changfengnan@bytedance.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).