Hey guys,
This is my first time posting to this list, and I am a newbie in Ceph
development.
I am trying to write new functions into librados.cc and call external
libraries from that very function.
My problem is that I can't get my head around this build system when
using ./run-make-check.sh
BUSINESS PROPOSAL ///
Dear, Do you speak English?
I wrote to you before, but you did not answer my mail. It important
business proposal, is worth $ 12.500,000 million for you, the fund
belongs my late client comes from your country, so contact me on my
official mailbox, to allow me to send you
On 14/02/2015 08:56, Gregory Farnum wrote:
On Fri, Feb 13, 2015 at 10:34 PM, Loic Dachary l...@dachary.org wrote:
Hi Greg,
I'm curious to know how you handle the flow of mails from QA runs. Here is a
wild guess:
* from time to time check that the nightlies run the suites that should be
Yeah. Well, the last run alone isn't so important; we want to see a
string of clean runs because a lot of issues aren't reproduced in
every run.
My hope was that we can see all green results for say this giant
release/backport, but I agree that we would need to make our go/no-go decision
Hi Yuri,
On 14/02/2015 17:22, Yuri Weinstein wrote:
Yeah. Well, the last run alone isn't so important; we want to see a
string of clean runs because a lot of issues aren't reproduced in
every run.
My hope was that we can see all green results for say this giant
release/backport, but I
Loic,
+1 - I like the way you're discussing:
v0.87.1-rc2
v0.87.1-rcX = v0.87.1 - is it easy to make this look like this after the
validation is completed?
BTW: When I re-run suites now for validation I use -s named_branch arg in
the command line. Maybe I should be using SHA ref instead? I
On 14/02/2015 22:53, Loic Dachary wrote:
Hi Yuri,
On 14/02/2015 17:22, Yuri Weinstein wrote:
Yeah. Well, the last run alone isn't so important; we want to see a
string of clean runs because a lot of issues aren't reproduced in
every run.
My hope was that we can see all green results for
