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| pw143749 [PATCH v2 4/4] devtools/test-meson-builds: use cross files for 32bit build
Date: Fri,  6 Sep 2024 13:05:45 -0400	[thread overview]
Message-ID: <20240906170545.3227071-1-robot@bytheb.org> (raw)
In-Reply-To: <20240906161244.1663967-5-bruce.richardson@intel.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2024-09-06 17:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240906161244.1663967-5-bruce.richardson@intel.com>
2024-09-06 15:45 ` |SUCCESS| pw143746-143749 " qemudev
2024-09-06 15:50 ` qemudev
2024-09-06 16:15 ` |WARNING| pw143749 " checkpatch
2024-09-06 17:05 ` 0-day Robot [this message]
2024-09-11  0:33 ` |SUCCESS| pw143746-143749 [PATCH] [v2,4/4] devtools/test-meson-build dpdklab
2024-09-11  1:03 ` dpdklab
2024-09-11  2:42 ` dpdklab
2024-09-11  4:50 ` |PENDING| " dpdklab
2024-09-11  5:29 ` |SUCCESS| " dpdklab
2024-09-11  5:30 ` dpdklab
2024-09-11  5:31 ` |PENDING| " dpdklab
2024-09-11  7:20 ` |SUCCESS| " dpdklab
2024-09-11  7:21 ` dpdklab
2024-09-11  7:26 ` dpdklab
2024-09-11  7:33 ` dpdklab
2024-09-11 10:04 ` |PENDING| " dpdklab
2024-09-11 10:42 ` |SUCCESS| " dpdklab
2024-09-11 11:42 ` dpdklab
2024-09-11 12:54 ` dpdklab
2024-09-11 13:23 ` dpdklab
2024-09-11 13:52 ` dpdklab
2024-09-11 14:12 ` dpdklab
2024-09-11 14:29 ` dpdklab
2024-09-11 15:26 ` dpdklab
2024-09-11 15:31 ` dpdklab
2024-09-11 17:58 ` dpdklab
2024-09-15 20:53 ` dpdklab
2024-09-16  2:21 ` 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=20240906170545.3227071-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).