►
From YouTube: 2019-11-19 :: Ceph Testing Meeting
Description
.
A
B
A
So
I'm
not
I'm
not
trying
to
discriminate
against
this
particular
PR,
but
I
started
yesterday,
because
Nia
asked
me
to
like
do
one
more
and
then
saying
hey
guys.
You
know
like
we
need
to
draw
the
line
because
I
would
love
to
keep
doing
that
forever
and
if
and
they
actually
wanted
to
release
it
before
the
things
given,
which
is
like
almost
no
time
right.
A
B
A
A
B
A
Please
because
I
think
I
forgot
to
lock
it
right.
That's
why
it
stuff
got
merged.
Today,
yeah
I
mean
essentially
like
that
that
that,
like
six
number
of
you
reviewers,
this
is
for
us,
as
a
kind
of
you
know,
flag,
saying,
like
that's
done
right
because
III,
you
know,
I
I
actually
started
building
release
candidates
because
it's
more
convenient
for
me
to
manage
like
my
branch,
as
opposed
to
run
it
on
the
top
of
the
tip
on
the
top
of
the
branch
yeah.
B
C
A
Mimic
I
think
it's
more
as
far
as
I'm
concerned
me
make
is
like
almost
done,
but
we
don't
have
a
approval
for
set
of
s
its
Patrick's
team
and
Patricks
team.
You
know
they
have
several
people
I,
don't
even
remember
all
their
names
but
like
Venky
and
somebody
else
like
three
people
and
I
think
then
they
just
didn't
get
used
to
the
process
of
like
approval,
etcetera
and
I
suspect
that
they
just
missed
that
mimic
approval
email.
A
So,
okay,
did
we
everything
in
IRC
I,
peeled
them
already
yesterday,
via
email
I
actually
took
like
I,
didn't
send
it
to
like
everybody,
I
just
send
it
to
them,
so
they
are
doing
that
right
now,
I
think
it's
almost
done
so
I
would
suspect
like
either
today
or
tomorrow.
We
will
be
able
to
say:
go
because,
like
I,
don't
see
any
like
based
on
like
high
level
the
amount
of
failures,
I,
don't
see
anything
crucial,
I,
don't
think
that
they
just
don't
know
what
what
to
say
so.
I
see.
A
That's
what
I
did
yesterday,
because,
when
Maneka
and
sage
started
kind
of
you
know
putting
pressure
on
me,
I
actually
pin
Patrick
and
II
actually
redirected
that
back
to
them,
because
he
said
unless
this
emergency,
it's
not
really
emergency,
because
it's
ready
almost
and
I
mean
I.
Don't
need
to
do
anything!
It's
matter
of
approved
and
built.
B
Alright
for
the
dashboard
PR
as
I'm
looking
at
I'm
looking
at
yeah,
so
we
have
to
it,
looks
like
the
the
first
one
is
the
one
I'm
going
to
merge
right
now,
that's
the
rgw
one
and
then
there's
the
internationalization
support,
you're
running
a
raid.
Us
do
a
run
on
that
that
way.
Yes,
but
you
know
I,
don't
know
what
priority
it's
300
jobs.
Maybe
you
want
to
cancel
it.
D
E
B
A
A
B
C
A
B
B
B
F
F
F
So
and
we've
got
a
situation
when
they
be
some
part
of
code,
is,
okay
is
workable,
but
unit
s
are
not
working
just
because
Alvin.
Indeed
the
unit
test
code.
It
is
such
a
way
it.
They
are
incompatible
and
I
need
to
do
more
work
as
much
as
three
times
so
even
four
times.
Just
because
two
marches
and
I
spend
too
much
to
try
to
understand
the
internals
of
mocks.
B
D
B
B
F
F
F
B
F
B
F
F
F
B
F
F
F
F
B
D
A
F
D
F
So,
okay,
so
I
found,
it
seems
like
the
reason
that
they
were
in
the
line
just
because
the
worker
were
failing.
So
I
found
a
bug
in
technology.
If
you
run
a
suite
with
two
touji
branch,
which
is
not
supported
like
witchy,
which
has
flashes
or
anything
else,
then
the
worker
is
dying
and
there
were
massive
outage
of
workers
on
SE
pehle.
What.
F
F
F
Yes,
it
it
was
out
of
sync
but
anyway,
so
the
tautology
code
is
failing,
I
mean
worker
code
because
it's
it's
God's
on
handle
exception
for
this
situation.
When
the
tautology
can't
check
to
check
out
this
branch,
the
test
rebel,
the
rebel
utils,
Johnny,
Bach
and
many
workers
were
collapsed
just
because
they
go
to
annex
and
this
exception
and
we're
out
of
the
service.
A
F
A
Know
just
Davis
I
mean
and
I
actually
not
exactly
in
the
loop
in
terms
of
how
we
updated
ology
I
mean
I,
have
data's
all
I,
think
well,
I'm
AI,
think
I'm,
lying
I
think
I'm
pulling
tautology
on
like
for
say,
PR
jobs
and
for
my
personal,
like
when
I
run
jobs
automatically
in
quanta
and
in
front
AB.
But
in
terms
of
how
workers
get
updated.
I
have
no
clue.