From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: humin29@huawei.com, robot@bytheb.org
Subject: [dpdk-test-report] |FAILURE| pw92473 [dpdk-dev] [PATCH 2/2] eventdev: fix memory leakage when create thread fail
Date: Fri, 30 Apr 2021 06:59:07 -0400 [thread overview]
Message-ID: <20210430105907.5626-1-robot@bytheb.org> (raw)
In-Reply-To: <1619775278-25857-3-git-send-email-humin29@huawei.com>
From: robot@bytheb.org
Test-Label: github-robot
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/92473/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/799058524
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"
####################################################################################
87/96 DPDK:fast-tests / thash_autotest FAIL 0.17 s (exit status 255 or signal 127 SIGinvalid)
88/96 DPDK:fast-tests / trace_autotest OK 0.17 s
89/96 DPDK:fast-tests / telemetry_json_autotest OK 0.17 s
90/96 DPDK:fast-tests / telemetry_data_autotest OK 0.17 s
91/96 DPDK:fast-tests / ring_pmd_autotest OK 0.17 s
92/96 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 0.62 s
93/96 DPDK:fast-tests / bitratestats_autotest OK 0.17 s
94/96 DPDK:fast-tests / latencystats_autotest OK 0.17 s
95/96 DPDK:fast-tests / pdump_autotest OK 5.23 s
96/96 DPDK:fast-tests / compressdev_autotest SKIP 0.17 s
Ok: 89
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-18.04-gcc-shared-abi+doc+tests at step "Build and test"
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2021-04-30 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1619775278-25857-3-git-send-email-humin29@huawei.com>
2021-04-30 9:35 ` [dpdk-test-report] |SUCCESS| pw92473 " checkpatch
2021-04-30 10:59 ` 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=20210430105907.5626-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=humin29@huawei.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).