automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: david.marchand@redhat.com, robot@bytheb.org
Subject: [dpdk-test-report] |FAILURE| pw90749 [dpdk-dev] [PATCH] build: list symbols exports in a single file
Date: Tue,  6 Apr 2021 13:57:06 -0400	[thread overview]
Message-ID: <20210406175706.29976-1-robot@bytheb.org> (raw)
In-Reply-To: <20210406163231.19663-1-david.marchand@redhat.com>

From: robot@bytheb.org

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

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

      parent reply	other threads:[~2021-04-06 17:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210406163231.19663-1-david.marchand@redhat.com>
2021-04-06 16:34 ` [dpdk-test-report] |SUCCESS| pw90749 " checkpatch
2021-04-06 17:55 ` [dpdk-test-report] |SUCCESS| pw90749 " 0-day Robot
2021-04-06 17:57 ` 0-day Robot [this message]

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=20210406175706.29976-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=david.marchand@redhat.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).