All of lore.kernel.org
 help / color / mirror / Atom feed
From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Bdev claim and single writer semantics
Date: Wed, 09 May 2018 17:32:05 +0000	[thread overview]
Message-ID: <1525887123.2784.56.camel@intel.com> (raw)
In-Reply-To: CANvN+enRaZdMMqnRQfmh1X5eh+t4KMsxryZgpP0+3rpdktLPWA@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 649 bytes --]

On Wed, 2018-05-09 at 08:12 +0000, Andrey Kuzmin wrote:
> Ben,
> 
> the patch hs been submitted a week back, and then updated to account for
> review coments, but I still don't see it merged. Is there anything I can do to
> make this happen?

Hi Andrey,

The patch is failing one of the tests. The test output is linked in the comments
of the review. I re-ran it a few times and it consistently fails. I don't think
the problem is going to end up being your change, but rather your change
invalidates some assumptions or expected behavior in one of the tests. That
needs to get debugged and resolved before we can merge.

Thanks,
Ben

             reply	other threads:[~2018-05-09 17:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 17:32 Walker, Benjamin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-09 21:57 [SPDK] Bdev claim and single writer semantics Walker, Benjamin
2018-05-09 17:58 Andrey Kuzmin
2018-05-09  8:12 Andrey Kuzmin
2018-05-02 22:07 Andrey Kuzmin
2018-05-02 16:45 Walker, Benjamin
2018-05-02 13:58 Luse, Paul E
2018-05-02 13:40 Andrey Kuzmin
2018-04-30 17:26 Andrey Kuzmin
2018-04-30 17:24 Walker, Benjamin
2018-04-28 21:35 Andrey Kuzmin
2018-04-28 21:30 Andrey Kuzmin
2018-04-28 21:13 Luse, Paul E
2018-04-27 23:06 Harris, James R
2018-04-27 15:04 Andrey Kuzmin
2018-04-26 23:26 Walker, Benjamin
2018-04-26 12:25 Andrey Kuzmin

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=1525887123.2784.56.camel@intel.com \
    --to=spdk@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.