►
From YouTube: SIG-Testing Weekly Meeting for 20220906
Description
SIG-Testing Weekly Meeting for 20220906
A
C
C
Yeah,
I
am
happy
to
wait
for
another
minute
or
two,
and
actually
I
mean
it's
1003
already,
I
say
having
hopped
on
a
bit
late,
but
I'm
also
happy
to
just
like
discuss
the
thing
from
last
time.
A
C
Yeah,
so
I
think
the
stuff
I
got
last
time
when
I
was
asking
around
about
like
sending
email
to
the
deathless
which
sorry
for
not
getting
back
earlier.
I
just
added
a
note
like
this
morning.
I
was
like
it
sounds
like
that
should
be
open
email
according
to
like
the
rest
of
my
teammates.
I
also
understand
if
you
want
the
like
notice
to
come
from
like
a
leader
chair
or
something
oh
cool,
hey
man,
my
agenda
today,
I
think.
A
Cool
sorry.
C
Okay,
yeah
so
feel
free
to
last
minute
add
some
stuff
to
the
agenda.
Folks,
if
you
want
otherwise,
I
think
we
just
have
the
one
thing
from
last
time,
since
the
meeting
got
hunted
so
notice
about
greenhouse
shut
down.
My
understanding
basically
is
like
it
sounds
like
anybody
can
send
a
notice
about
that,
but
if,
like
or
not,
if
you
don't
wanna,
send
that
like
email
directly
or
something,
I
think
I
I'm
either
happy
to
send
it
or
like
find
somebody
to
send
a
notice.
C
I
think
the
other
question
was
just
like
it
sounded
like.
There
was
a
bit
of
confusion
over
whether
a
notice
needed
to
be
sent
about
this
or
not.
So
is
this
more
of
like
a
friendly
heads
up
or
is
this
more
of
like
a?
We
definitely
need
to
notify
folks
before
turning
that
down.
B
Well,
this
is
just
a
notification
because
we
disabled
usage
of
green
greenhouse
in
basically
testing
for
our
for
most,
and
I
spend
some
time
doing
cleanup
about
basic
preset
related
to
this
related
grid.
Now,
so
the
idea
is
to
send
a
notification
and
say
we're
gonna,
shut
down
the
service
and
basically
delete
all
the
resources.
D
I
actually
think
we're
okay
at
this
point
to
just
shut
it
down,
we've
reached
out
to
the
specific
projects
that
we
know
are
using
it
and
if
someone
else
was
using
it
and
wants
to
know,
I
mean
the
build
process
should
be
durable
to
the
like
to
the
cache
being
missing
and
they
can
always
come
file
a
bug
with
test
infra
or
you
know,
cincinnati
center.
For
a
case,
I
o-
and
let
us
know
that,
like
hey,
they
you
know
want
that
back.
D
But
at
this
point
we
shouldn't
have
any
ongoing
usage
and
no
one
should
be
broken
by
it
being
gone.
It
should
just
fall
back
to
local
as
if
it
had
a
cache
miss
which
I
know
cops.
B
Cops
folks
basically
keep
that
label
for
some
old
version
that
he
cops
1.1.
They
basically
decide
to
maintain
the
level
for
whatever
reason.
So
the
idea
is
to
just
give
a
notice
to
in
the
dev
list
and
say:
oh,
we
should
have
greenhouse
by
end
of
the
month.
If
you
have
an
issue
wish
up
just
that.
So
now
we
talk
about
just
the
aster
flag.
Oh,
if
a
tech
lead
of
c
check
can
do
that.
That
would
be
great,
or
I
can
do
that
if
needed,.
D
D
It
shouldn't
affect
most
of
most
of
dev,
and
if
anyone
is
impacted,
I
mean
it's
just
a
little
bit
slower
build,
and
that
was
that's
always
possible
using
this,
because
you
know
we
made
no
guarantees
about
longevity
of
the
cash
when
kubernetes
was
using
it
and
building
I
mean
we
were
flushing
the
cash
on
like
at
least
a
daily
basis,
just
because
of
the
volume
even
with
throwing
like
the
terabytes
at
it,
just
the
amount
of
like
poorly
cached
artifacts
that
fill
the
fillet.
D
You
know
most
of
it
was
being
flushed
very
frequently.
So
if
you're
a
smaller
project
building
infrequently,
you
might
not
have
ever
really
seen
a
lot
of
benefit
to
trying
to
use
this,
since
it
was
a
shared
instance
and
you'd
have
a
lot
less
accesses
than
the
things
that
were
caching
well
in
kubernetes.
A
D
C
Yeah
thanks
for
doing
this
yeah
for
what
it's
worth.
I
think
what
ben
has
said
lines
up
with
what
I've
heard
from
like
some
other
books
like
cole
or
whatnot.
It's
just
like
it.
It
sounds
like
the
usage,
is
non-problematic
and
can
just
be
turned
down
without
notifying.
D
D
I
think
that
might
be
it
at
this
point:
google
cloud
provider
cloud
provider
gcp.
I
don't
think
any
other
project
has
any
remaining
on
current
development.
B
D
There's
there's
one
or
two
other
projects
that
have
it
but
they're,
not
they
don't
appear
to
be
using
the
the
cache
I'm
just
using
our
code
search
to
check
for
build
files.
A
D
Repo
infrastill
provides
it
because
it
because
it
was
itself
a
bazel
package
and
then
there's
some
stuff
in
vendor,
which
is
ignorable.
D
Yeah,
I
don't
think
any
of
these
are
like
actively,
maybe
cube
builder,
but
they're,
not
the
labels
that
you're
seeing
everywhere
are
just
bad
copy,
paste
inheritance
on
the
on
the
jobs.
When
I
took
a
pass
last
time,
just
lots
and
lots
and
lots
of
ci
jobs.
They
were
also
still
setting
like
the
local
scratcher
and
just
I
mean
people
just
copy
over
all
the
labels,
because
I
mean
it's
not
like
they're
well,
documented
or
anything
to
begin
with
so
or
very
discoverable.
B
That's
why
a
notice
would
be,
I
suggest,
notice,
because
we
don't
have
the
full
scope
of
people
using
that
out
of
this
world,
investigate
the
entire
code
code
base
for
over
the
four
get
a
break
organization.
Just
and
notice
might
be
great
to
just
basically
say
to
people.
We
did.
We
shouldn't
clean
ours,
make
sure
we
you
don't
use
that
in
your
bezel
configuration.
D
Yeah
I
mean
these
aren't
active
like
like,
for
example,
q
builder
has
some
bazel
files,
but
their
workspace
file
has
not
been
touched
in
four
years
so
like
that
they're,
definitely
not
actually
building
that
this
no
way
right.
That
would
mean
they
have
an
updated
go
for
years.
For
example,.
D
D
And
I
mean
even
if
they
were
at
some
point,
we
just
got
to
cut
it
off
it,
the
it's
you
know
reasonably
expensive
to
run
and
we
never
inten,
we
kind
of
never
intended
for
it
to
be
for
these
projects.
We
just
permitted
it.
D
We
I
spent
it
up
like
I
built
this
and
I
span
it
up
for
kubernetes,
and
then
we
also
pilot
with
test
infra
and
then
I
think
cops
picked
it
up,
but
it
was
always
kind
of
like
this
is
going
to
be
best
effort
and
you're
going
to
get
fairly
stomped
by
kubernetes.
So.
D
B
A
D
D
A
A
C
C
I
mean
I'm
happy
to
talk
about
test
grid.
I
don't
have.
I
don't
have
any
specific
item
on
it,
but
if
you
have
questions
or
anything
feel
free.
C
Oh
heck
yeah,
then
yeah
part
of
part
of
the
other
thing
is
like
I.
I
can
say
that,
like
actually,
I
haven't
been
doing
a
lot
in
the
open
source
side
of
it
recently,
except
for
like
some
random
fixes,
but
I
I
do
intend
to
try
and
make
it
easier
for
folks
to
like
either
learn
more
contribute
in
general,
regardless
whether
it's
like
internal
or
open
source,
so
yeah
definitely
hit
me
up
without
ideas
or
anything
like
that.
B
Well,
the
idea
is
kind
of
simple
rebuild:
that's
good
in
the
open
from
scratch,
because
it's
not
world
fight
internally
but
open
source
it.
So
the
idea
is
to
make
it
like
a
lantern
ship
cover
by
let
linux
foundation's
licensing
foundation
program,
make
it
like
an
internship
and
trying
to
build
something
in
the
open.
A
E
Oh
god,
sorry,
I'm
all
camera
off.
I've
got
to
load.
I've
got
power.
Failure
on
this
side.
No,
I
I
go
to
the
that
contributor
from
lfx
quite
often
and
they're
keen
to
have
all
sorts
of
mental
things
going.
So
if
you
want
somebody
to
to
work
on
that
as
a
mentee
and
actually
do
buy
them
a
step
and
for
it.
C
C
Cool
yeah
that
I
think
we're
starting
to
try
and
plan
for
like
next
year
or
whatnot,
so
cool.
C
Yeah
go
for
it,
see
ya
yeah,
and
I
think
similarly,
we
can
probably
cut
this
off
unless
somebody
is
anything
else
they
want
to
discuss.