All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Samuel Just <sjust@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Merging rados related backports
Date: Fri, 5 Aug 2016 15:08:36 +0200	[thread overview]
Message-ID: <57A48FD4.40401@dachary.org> (raw)

Hi Sam,

When running the rados suite on a given backport targetting jewel (or hammer for that matter, but it's less of an issue) I figured the smallest subset would be enough to guarantee there is no trivial regression, this is why we're routinely using X/2000. I understand this is not enough coverage to release jewel and we have the nightlies running X/14 for that. When jewel is eventually released, all of the rados suite should have been run.

If you think there are too many regressions merged in the jewel branch because X/2000 did not detect them, we will increase the size of the subset. This will slow down backporting when the lab is misbehaving, but that's less time consuming than chassing a regression long after the guilty commit has been merged.

Cheers

[1] http://tracker.ceph.com/projects/ceph-releases/wiki/Sepia/97

-- 
Loïc Dachary, Artisan Logiciel Libre

                 reply	other threads:[~2016-08-05 13:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=57A48FD4.40401@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sjust@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.