From: Yuri Weinstein <yweinste@redhat.com>
To: Loic Dachary <loic@dachary.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: giant integration branch for v0.87.1 ready for QE
Date: Fri, 20 Feb 2015 16:49:32 -0500 (EST) [thread overview]
Message-ID: <1622340604.24695270.1424468972740.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1387059957.19365485.1424108024488.JavaMail.zimbra@redhat.com>
Team leads,
Please review QE validation results summary in http://tracker.ceph.com/issues/10501
Loic - this RC looks ready for release (in my opinion) !
Thx
YuriW
----- Original Message -----
From: "Yuri Weinstein" <yweinste@redhat.com>
To: "Loic Dachary" <loic@dachary.org>
Cc: "Ceph Development" <ceph-devel@vger.kernel.org>
Sent: Monday, February 16, 2015 9:33:44 AM
Subject: Re: giant integration branch for v0.87.1 ready for QE
I have completed suites execution on giant branch (v0.87.1 RC)
All results are summarized in http://tracker.ceph.com/issues/10501 under "QE VALIDATION" section.
Some suites had to be run more then ones due to environment noise.
Two suites are being re-run now - upgrade:firefly-x and powecycle.
Next steps:
- the team leads to review/confirm results
- Loic - can you review and triage issues as needed.
- two suites require results analysis:
multimds
rados (two known tickets, but need more checking) ## 10209, 9891
krbd (two new tickets, but need more checking) ## 10889, 10890
Thx
YuriW
----- Original Message -----
From: "Loic Dachary" <loic@dachary.org>
To: "Yuri Weinstein" <yweinste@redhat.com>
Cc: "Ceph Development" <ceph-devel@vger.kernel.org>
Sent: Wednesday, February 11, 2015 7:30:06 AM
Subject: Re: giant integration branch for v0.87.1 ready for QE
Hi Yuri,
The giant-backports pull requests were merged into https://github.com/ceph/ceph/tree/giant which is not ready for testing.
For the record, the head is https://github.com/ceph/ceph/commit/78c71b9200da5e7d832ec58765478404d31ae6b5
Cheers
On 10/02/2015 18:20, Loic Dachary wrote:
> Hi Yuri,
>
> The giant integration branch for v0.87.1 as found at https://github.com/ceph/ceph/commits/giant-backports has been approved by Yehuda, Josh and Sam and is ready for QE.
>
> For the record, the head is https://github.com/ceph/ceph/commit/6b08a729540c61f3c8b15c5a3ce9382634bf800c
>
> Cheers
>
--
Loïc Dachary, Artisan Logiciel Libre
--
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
next prev parent reply other threads:[~2015-02-20 21:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 17:20 giant integration branch for v0.87.1 ready for QE Loic Dachary
2015-02-11 15:30 ` Loic Dachary
2015-02-11 17:22 ` Yuri Weinstein
2015-02-11 18:03 ` Loic Dachary
2015-02-11 22:33 ` Yuri Weinstein
2015-02-16 17:33 ` Yuri Weinstein
2015-02-16 18:02 ` Sage Weil
[not found] ` <CAC6JEv8LEV5bNaoW3__2hjfYNZRmXDScp-a_1V+AKiX_SwWQCQ@mail.gmail.com>
2015-02-16 18:49 ` Yuri Weinstein
2015-02-20 21:49 ` Yuri Weinstein [this message]
2015-03-10 6:56 ` giant integration branch for v0.87.1 ready for QE / fix for 10433/8011 ? osd/ReplicatedPG.cc: 5545: FAILED assert(soid < scrubber.start || soid >= scrubber.end) Laurent GUERBY
2015-03-10 7:59 ` Loic Dachary
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=1622340604.24695270.1424468972740.JavaMail.zimbra@redhat.com \
--to=yweinste@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.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.