All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abhishek Lekshmanan <abhishek@suse.com>
To: ceph-devel@vger.kernel.org
Cc: Sage Weil <sage@newdream.net>,
	Matt Benjamin <mbenjamin@redhat.com>,
	"Sadeh-Weinraub, Yehuda" <yehuda@redhat.com>,
	"Dillaman, Jason" <dillaman@redhat.com>,
	Patrick Donnelly <pdonnell@redhat.com>,
	"Durgin, Josh" <jdurgin@redhat.com>
Subject: Re: 12.2.2 status
Date: Thu, 26 Oct 2017 18:47:08 +0200	[thread overview]
Message-ID: <87d159dfg3.fsf@suse.com> (raw)
In-Reply-To: <87fua6c4xy.fsf@suse.com>



Also created a label to track the current PRs already tested
https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+label%3Awip-abhi-testing

> A first round of PRs were tested on Luminous integration branch, results
> updated at http://tracker.ceph.com/issues/21830,
> RADOS suite was green, RBD, RGW & FS hit some known failures
>
> ceph-disk has hit a failure with dmcrypt, details at
> http://tracker.ceph.com/issues/21830#note-10 which doesn't seem to have
> occured in QE runs before but there is a bug report, is anyone aware of
> past issues with ceph-disk & dmcrypt?
>
> Also for the leads, Sage, Yehuda. Jason, Josh, Patrick are there any
> critical PRs that we need to have in 12.2.2 so that we can include
> them in the next round of testing before handing over to QE?
>
> Best,
> Abhishek & Karol
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

-- 
Abhishek Lekshmanan
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)

  parent reply	other threads:[~2017-10-26 16:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 15:19 12.2.2 status Abhishek Lekshmanan
2017-10-26 15:40 ` Jason Dillaman
2017-10-26 22:38   ` Karol Mroz
2017-10-26 22:42     ` Jason Dillaman
2017-10-27 14:02       ` Jason Dillaman
2017-10-30  8:28         ` kefu chai
2017-10-30 13:09         ` Jason Dillaman
2017-10-26 16:14 ` Sage Weil
2017-10-26 16:47 ` Abhishek Lekshmanan [this message]
2017-10-26 16:50 ` Yehuda Sadeh-Weinraub
2017-10-26 22:48   ` Karol Mroz
2017-10-27 13:57     ` Casey Bodley
2017-10-30 20:38       ` Karol Mroz
2017-10-26 18:05 ` Patrick Donnelly
2017-11-03 17:44   ` Abhishek Lekshmanan
2017-11-03 17:53     ` Sage Weil
2017-11-03 18:02       ` Abhishek Lekshmanan
2017-11-03 20:54         ` kefu chai
2017-11-04  7:51           ` Nathan Cutler
2017-11-05 12:17             ` Abhishek L
2017-11-06  8:52               ` kefu chai
2017-11-06  9:57                 ` Abhishek Lekshmanan
2017-11-06 18:29                   ` Abhishek Lekshmanan
2017-11-06 19:55                     ` Patrick Donnelly
2017-11-07 21:59                       ` Abhishek
2017-11-07 23:09                         ` Patrick Donnelly
2017-11-07 23:51                         ` Matt Benjamin

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=87d159dfg3.fsf@suse.com \
    --to=abhishek@suse.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dillaman@redhat.com \
    --cc=jdurgin@redhat.com \
    --cc=mbenjamin@redhat.com \
    --cc=pdonnell@redhat.com \
    --cc=sage@newdream.net \
    --cc=yehuda@redhat.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 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.