DPDK CI discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: Dmitry Kozlyuk <dkozlyuk@oss.nvidia.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] |FAILURE| pw102055 [dpdk-dev] [PATCH v8 4/4] net/mlx5: support mempool registration
Date: Mon, 18 Oct 2021 13:41:34 -0400	[thread overview]
Message-ID: <f7tczo25iy9.fsf@redhat.com> (raw)
In-Reply-To: <CH0PR12MB5091B5436051F34BE34ED9BAB9BC9@CH0PR12MB5091.namprd12.prod.outlook.com> (Dmitry Kozlyuk's message of "Mon, 18 Oct 2021 16:29:30 +0000")

Dmitry Kozlyuk <dkozlyuk@oss.nvidia.com> writes:

>> -----Original Message-----
>> From: Dmitry Kozlyuk
>> Sent: 18 октября 2021 г. 19:05
>> To: ci@dpdk.org
>> Subject: RE: |FAILURE| pw102055 [dpdk-dev] [PATCH v8 4/4] net/mlx5:
>> support mempool registration
>> 
>> Hello,
>> 
>> I can't reproduce mempool_autotest failure locally.
>> Are test detailed logs published somewhere?
>> Or the only way is to wait for the community lab results?
>
> Never mind, found the link in "Summary" section of the GitHub report.

Glad you were able to find the link.

For future travelers, the Github Actions summary page contains archives
of the testlot.txt file.  Some scrolling might be required (I don't
think the interface is very user friendly in that regard).


      reply	other threads:[~2021-10-18 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211018144059.3303406-5-dkozlyuk@nvidia.com>
     [not found] ` <20211018151928.8564-1-robot@bytheb.org>
2021-10-18 16:05   ` Dmitry Kozlyuk
2021-10-18 16:29     ` Dmitry Kozlyuk
2021-10-18 17:41       ` Aaron Conole [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=f7tczo25iy9.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=dkozlyuk@oss.nvidia.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).