automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw139080 [PATCH v1] vhost: fix crash caused by accessing a freed vsocket
Date: Wed,  3 Apr 2024 13:06:02 -0400	[thread overview]
Message-ID: <20240403170602.3494087-1-robot@bytheb.org> (raw)
In-Reply-To: <TYAP286MB06494783C3973058BF499642D83D2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/139080/

_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8542180811

  parent reply	other threads:[~2024-04-03 17:06 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <TYAP286MB06494783C3973058BF499642D83D2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
2024-04-03 15:43 ` qemudev
2024-04-03 15:48 ` qemudev
2024-04-03 16:07 ` checkpatch
2024-04-03 16:54 ` |SUCCESS| pw139080 [PATCH] [v1] vhost: fix crash caused by accessing dpdklab
2024-04-03 16:55 ` dpdklab
2024-04-03 16:56 ` dpdklab
2024-04-03 16:56 ` dpdklab
2024-04-03 16:57 ` dpdklab
2024-04-03 16:57 ` dpdklab
2024-04-03 16:57 ` dpdklab
2024-04-03 16:57 ` dpdklab
2024-04-03 16:58 ` dpdklab
2024-04-03 16:58 ` dpdklab
2024-04-03 16:58 ` dpdklab
2024-04-03 16:58 ` dpdklab
2024-04-03 16:58 ` dpdklab
2024-04-03 16:59 ` dpdklab
2024-04-03 16:59 ` dpdklab
2024-04-03 17:04 ` dpdklab
2024-04-03 17:04 ` dpdklab
2024-04-03 17:04 ` dpdklab
2024-04-03 17:05 ` dpdklab
2024-04-03 17:05 ` dpdklab
2024-04-03 17:05 ` dpdklab
2024-04-03 17:05 ` dpdklab
2024-04-03 17:05 ` dpdklab
2024-04-03 17:05 ` dpdklab
2024-04-03 17:05 ` dpdklab
2024-04-03 17:05 ` dpdklab
2024-04-03 17:06 ` 0-day Robot [this message]
2024-04-03 17:06 ` dpdklab
2024-04-03 17:06 ` dpdklab
2024-04-03 17:06 ` dpdklab
2024-04-03 17:06 ` dpdklab
2024-04-03 17:06 ` dpdklab
2024-04-03 17:09 ` dpdklab
2024-04-03 17:09 ` dpdklab
2024-04-03 17:10 ` dpdklab
2024-04-03 17:10 ` dpdklab
2024-04-03 17:10 ` dpdklab
2024-04-03 17:10 ` dpdklab
2024-04-03 17:11 ` dpdklab
2024-04-03 17:11 ` dpdklab
2024-04-03 17:11 ` dpdklab
2024-04-03 17:11 ` dpdklab
2024-04-03 17:11 ` dpdklab
2024-04-03 17:11 ` dpdklab
2024-04-03 17:12 ` dpdklab
2024-04-03 17:12 ` dpdklab
2024-04-03 17:12 ` dpdklab
2024-04-03 17:12 ` dpdklab
2024-04-03 17:13 ` dpdklab
2024-04-03 17:15 ` dpdklab
2024-04-03 17:16 ` dpdklab
2024-04-03 17:16 ` dpdklab
2024-04-03 17:16 ` dpdklab
2024-04-03 17:16 ` dpdklab
2024-04-03 17:17 ` dpdklab
2024-04-03 17:17 ` dpdklab
2024-04-03 17:22 ` dpdklab
2024-04-03 17:23 ` dpdklab
2024-04-03 17:25 ` dpdklab
2024-04-03 17:26 ` dpdklab
2024-04-03 17:26 ` dpdklab
2024-04-03 17:26 ` dpdklab
2024-04-03 17:27 ` dpdklab
2024-04-03 17:27 ` dpdklab
2024-04-03 17:27 ` dpdklab
2024-04-03 17:30 ` dpdklab
2024-04-03 17:33 ` dpdklab
2024-04-03 17:34 ` dpdklab
2024-04-03 17:34 ` dpdklab
2024-04-03 17:35 ` dpdklab
2024-04-03 17:35 ` dpdklab
2024-04-03 17:35 ` dpdklab
2024-04-03 17:36 ` dpdklab
2024-04-03 17:59 ` dpdklab
2024-04-03 18:15 ` dpdklab
2024-04-03 18:15 ` dpdklab
2024-04-03 18:38 ` dpdklab
2024-04-03 18:39 ` dpdklab
2024-04-03 18:45 ` dpdklab
2024-04-03 19:27 ` dpdklab
2024-04-03 22:34 ` dpdklab
2024-04-04  8:04 ` dpdklab
2024-04-04  8:12 ` dpdklab
2024-04-04  8:17 ` dpdklab
2024-04-04  8:22 ` dpdklab
2024-04-04  8:42 ` dpdklab

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=20240403170602.3494087-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --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).