automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: zhichaox.zeng@intel.com, robot@bytheb.org
Subject: |FAILURE| pw124096 [PATCH v3] net/iavf: enable Tx outer checksum offload on avx512
Date: Thu, 16 Feb 2023 22:59:19 -0500	[thread overview]
Message-ID: <20230217035919.2692691-1-robot@bytheb.org> (raw)
In-Reply-To: <20230217014924.385709-1-zhichaox.zeng@intel.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4199948897
Build Logs:
-----------------------Summary of failed steps-----------------------
"fedora:35" failed at step Pull and prepare a fresh image
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "fedora:35" at step Pull and prepare a fresh image
####################################################################################
####################################################################################
#### [End job log] "fedora:35" at step Pull and prepare a fresh image
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2023-02-17  2:59 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230217014924.385709-1-zhichaox.zeng@intel.com>
2023-02-17  1:34 ` |SUCCESS| " qemudev
2023-02-17  1:38 ` qemudev
2023-02-17  1:46 ` checkpatch
2023-02-17  3:59 ` 0-day Robot [this message]
2023-02-17  3:14 |FAILURE| pw124096 [PATCH] [v3] " dpdklab
2023-02-17  3:16 dpdklab
2023-02-17  3:20 dpdklab
2023-02-17  3:34 dpdklab
2023-02-17  3:45 dpdklab
2023-02-17  3:47 dpdklab
2023-02-17  3:52 dpdklab
2023-02-17  3:54 dpdklab
2023-02-17  3:58 dpdklab
2023-02-17  4:00 dpdklab
2023-02-17  4:02 dpdklab
2023-02-17  4:16 dpdklab
2023-02-17  4:16 dpdklab
2023-02-17  4:22 dpdklab
2023-02-17  4:23 dpdklab
2023-02-17  4:34 dpdklab
2023-02-17  4:35 dpdklab
2023-02-17  4:36 dpdklab
2023-02-17  4:37 dpdklab
2023-02-17  4:45 dpdklab
2023-02-17  4:46 dpdklab
2023-02-17  4:52 dpdklab
2023-02-17  4:54 dpdklab
2023-02-17  4:56 dpdklab
2023-02-17  4:57 dpdklab
2023-02-17  4:58 dpdklab
2023-02-17  5:37 dpdklab
2023-02-17  5:41 dpdklab
2023-02-17  5:42 dpdklab
2023-02-17  5:43 dpdklab
2023-02-17  5:52 dpdklab
2023-02-17  5:54 dpdklab
2023-02-17  5:55 dpdklab
2023-02-17  5:56 dpdklab
2023-02-17  5:58 dpdklab
2023-02-17  6:00 dpdklab
2023-02-17  6:02 dpdklab
2023-02-17  6:05 dpdklab
2023-02-17  6:05 dpdklab
2023-02-17  6:08 dpdklab
2023-02-17  6:08 dpdklab
2023-02-17  6:12 dpdklab
2023-02-17  6:16 dpdklab
2023-02-17  6:16 dpdklab
2023-02-17  9:16 dpdklab
2023-02-17  9:22 dpdklab
2023-02-17  9:25 dpdklab
2023-02-17  9:28 dpdklab
2023-02-17  9:33 dpdklab
2023-02-17  9:36 dpdklab
2023-02-17  9:37 dpdklab
2023-02-17  9:37 dpdklab
2023-02-17  9:39 dpdklab
2023-02-17  9:43 dpdklab
2023-02-17  9:49 dpdklab
2023-02-17  9:55 dpdklab
2023-02-17  9:55 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=20230217035919.2692691-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=test-report@dpdk.org \
    --cc=zhichaox.zeng@intel.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).