From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: wangyunjian@huawei.com, robot@bytheb.org
Subject: |FAILURE| pw126977 [dpdk-dev] [PATCH 1/1] net/txgbe: fix use-after-free on remove
Date: Thu, 18 May 2023 04:00:10 -0400 [thread overview]
Message-ID: <20230518080010.277394-1-robot@bytheb.org> (raw)
In-Reply-To: <06a89892aa1b37996e5e629b3488c59d565393bd.1684393730.git.wangyunjian@huawei.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/126977/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/5011582483
Build Logs:
-----------------------Summary of failed steps-----------------------
"fedora:35-gcc" failed at step Fail if no image (not supposed to happen)
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "fedora:35-gcc" at step Fail if no image (not supposed to happen)
####################################################################################
####################################################################################
#### [End job log] "fedora:35-gcc" at step Fail if no image (not supposed to happen)
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2023-05-18 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <06a89892aa1b37996e5e629b3488c59d565393bd.1684393730.git.wangyunjian@huawei.com>
2023-05-18 7:01 ` |SUCCESS| pw126977 " qemudev
2023-05-18 7:05 ` qemudev
2023-05-18 7:12 ` checkpatch
2023-05-18 8:00 ` 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=20230518080010.277394-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=test-report@dpdk.org \
--cc=wangyunjian@huawei.com \
/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).