►
From YouTube: Kubernetes SIG Testing 2017-06-20
Description
Meeting notes: https://docs.google.com/document/d/1z8MQpr_jTwhmjLMUaqQyBk1EYG_Y_3D4y4YdMJ7V1Kk
A
Hello
today
is
June
20th.
This
is
the
big
test
meeting
and
right
now
we
kind
of
have
a
light
agenda
so
folks
have
any
other
things
to
talk
about,
feel
free
to
bring
them
up.
Aaron
was
going
to
talk
about
the
1
7
release,
update
of
the
current
state
of
things.
I
know
if
you
had
any
color
to
add
to
that
Verve.
B
We're
chronically
trying
to
get
things
in
the
state
where
we
can
lift
code
freeze,
maybe
by
tomorrow
I
think
the
major
blocker
is
upgrade
tests
harden
where
and
we
solve
a
lot
about
setting
bugs
it.
I
don't
know
seems
like
every
time.
This
is
mulling.
My
second
release,
where
I'm
like
involved
in
release
process-
and
it
seems
like
we
just
have
like
endless
amount
of
things-
are
just
like
there
are
more
FS
and
people,
so
people
care
about
some
things.
Other
people,
just
you
know,
they're
still,
release
blocking
and
I
was
working
on
them.
A
Yeah
there's
there
seems
to
be
a
contentious
ownership
problem.
I
was
able
to
be
spawned
off
ones
that
were
assigned
to
me
directly
to
other
people
to
have
time
to
take
a
look
at
them
and
weep
unto
them
out
of
the
release
of
these.
For
this
point,
because
it's
too
flaky
but
people
did
inspect
and
triage.
A
This
point,
the
only
other
agenda
item
that
is
for
this
week
was
to
go
through
the
potential
list
of
1/8
roadmap
items
have
folks
at
all
taking
a
look
at
some
of
those
things
or
had
comments
or
questions
on
them.
I
know:
Eric
had
a
fairly
extensive
list,
I,
don't
know
exactly
who
is
going
to
all
be
able
to
be
resource
to
execute
on
some
of
this
stuff.
A
C
C
A
D
Hey
this,
is
you
I,
don't
think
it's
on
the
1/8
items
budget
see
in
the
dark?
There
was
some
talk
about
getting
a
unit
output
for
the
test.
Cmd'
stuff.
Do
you
guys
have
if
I
did
whatever
posed
in
origin?
I
had
written
a
sort
of
I
mean
there's
like
a
bash
framework
for
testing,
which
is
hilarious
and
wonderful,
but
it
outputs
a
pretty
pretty
bull
format,
o'the
output
and
from
that
we
generated
a
unit
for
our
testing.
D
A
Think
stuff
like
that,
would
I
doubt
we'll
go
into
the
main
library
posit
or
e
I
mean
someone
could
correct
me
from
wrong
there,
but
the
I
would
probably
work
with
Ryan
who's
here
and
also
talk
with
Eric
on
probably
getting
if
you
wanted
to
getting
it
into
the
testing
it
tested
for
repo
right.
D
We
have
had
some
conversations
downstream
about
dishing
batch
all
together.
I
think
the
origin
of
those
sweets
is
being
a
really
quick
thing
that
just
starts
the
Atty
server
and
tests
see
like
accountability
was
I
think
it
was
good
before,
but
we
almost
were
thinking
of
just
using
ginkgo
for
all
of
that,
so
I'm
not
sure.
If,
like
what
long-term
ideas
you
guys
have,
if
you
want
to
stick
with
bash
for
testing
B
or
not,
we.
C
A
Well,
I,
in
a
long
haul
coup
vidiian
was
meant
to
be
the
foundational
piece
that
a
top
of
which
all
the
other
pieces
would
be
built.
That's
the
objective
when
we
get
to
a
point
where
everyone's
happy
enough
to
replace
all
the
stuff
is
another
TBD
item
and
I.
Think
those
who
own
the
kuba
script
or
e
stuff
would
have
to
determine
one.
That
point
is.