automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: stephen@networkplumber.org, robot@bytheb.org
Subject: |FAILURE| pw159697 [PATCH v3 7/7] pcapng: improve performance of timestamping
Date: Mon, 12 Jan 2026 00:44:59 -0500	[thread overview]
Message-ID: <20260112054459.934295-1-robot@bytheb.org> (raw)
In-Reply-To: <20260112045359.142999-8-stephen@networkplumber.org>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2026-01-12  5:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260112045359.142999-8-stephen@networkplumber.org>
2026-01-12  4:56 ` |SUCCESS| " checkpatch
2026-01-12  5:01 ` |SUCCESS| pw159691-159697 " qemudev
2026-01-12  5:08 ` qemudev
2026-01-12  5:44 ` 0-day Robot [this message]
2026-01-12  9:53 ` |SUCCESS| pw159691-159697 [PATCH] [v3,7/7] pcapng: improve performan dpdklab
2026-01-12  9:53 ` |PENDING| " dpdklab
2026-01-12  9:53 ` |FAILURE| " dpdklab
2026-01-12  9:56 ` dpdklab
2026-01-12  9:57 ` |SUCCESS| " dpdklab
2026-01-12  9:58 ` |FAILURE| " dpdklab
2026-01-12 10:02 ` |SUCCESS| " dpdklab
2026-01-12 10:07 ` |PENDING| " dpdklab
2026-01-12 10:07 ` dpdklab
2026-01-12 10:13 ` |SUCCESS| " dpdklab
2026-01-12 10:15 ` dpdklab
2026-01-12 10:17 ` |FAILURE| " dpdklab
2026-01-12 10:22 ` |SUCCESS| " dpdklab
2026-01-12 10:30 ` |WARNING| " dpdklab
2026-01-12 10:35 ` |SUCCESS| " dpdklab
2026-01-12 10:52 ` dpdklab
2026-01-12 11:54 ` dpdklab
2026-01-12 15:35 ` dpdklab
2026-01-12 16:38 ` |FAILURE| " dpdklab
2026-01-12 16:41 ` dpdklab
2026-01-12 17:22 ` |WARNING| " dpdklab
2026-01-12 17:31 ` |SUCCESS| " 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=20260112054459.934295-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=stephen@networkplumber.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).