automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: scott.k.mitch1@gmail.com, robot@bytheb.org
Subject: |FAILURE| pw159689 [PATCH v4 2/2] mailmap: add Scott Mitchell
Date: Sun, 11 Jan 2026 12:42:15 -0500	[thread overview]
Message-ID: <20260111174215.1471329-1-robot@bytheb.org> (raw)
In-Reply-To: <20260111160626.2103-3-scott.k.mitch1@gmail.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/159689/

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/20898722114

  parent reply	other threads:[~2026-01-11 17:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260111160626.2103-3-scott.k.mitch1@gmail.com>
2026-01-11 16:07 ` |SUCCESS| " checkpatch
2026-01-11 17:00 ` |FAILURE| pw159688-159689 " qemudev
2026-01-11 17:42 ` 0-day Robot [this message]
2026-01-12  0:17 ` |FAILURE| pw159688-159689 [PATCH] [v4,2/2] mailmap: add Scott Mitche dpdklab
2026-01-12  0:19 ` dpdklab
2026-01-12  0:20 ` dpdklab
2026-01-12  0:21 ` |WARNING| " dpdklab
2026-01-12  0:23 ` |FAILURE| " dpdklab
2026-01-12  0:35 ` dpdklab
2026-01-12  0:41 ` |SUCCESS| " dpdklab
2026-01-12  1:45 ` |FAILURE| " dpdklab
2026-01-12  1:45 ` dpdklab
2026-01-12  2:13 ` |WARNING| " dpdklab
2026-01-12  2:40 ` |FAILURE| " dpdklab
2026-01-12  4:06 ` dpdklab
2026-01-12  4:24 ` dpdklab
2026-01-12 15:39 ` dpdklab
2026-01-12 15:45 ` dpdklab
2026-01-12 15:56 ` |SUCCESS| " dpdklab
2026-01-12 15:56 ` |FAILURE| " dpdklab
2026-01-12 16:30 ` dpdklab
2026-01-12 16:45 ` dpdklab
2026-01-12 16:53 ` dpdklab
2026-01-12 17:27 ` |WARNING| " dpdklab
2026-01-12 17:49 ` |FAILURE| " dpdklab
2026-01-12 18:08 ` |SUCCESS| " dpdklab
2026-01-12 18:53 ` |FAILURE| " dpdklab
2026-01-12 19:30 ` 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=20260111174215.1471329-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=scott.k.mitch1@gmail.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).