►
From YouTube: SIG-Testing Biweekly Meeting for 20230403
Description
SIG-Testing Biweekly Meeting for 20230403
A
A
A
A
A
That's
true,
I'm,
a
newcomer
to
the
chair,
rule
I,
don't
think
it's
been
published
yet,
but
it's
been
discussed
plenty
and
I'm
very
glad
to
see
that
Michelle
is
sticking
around
and
that
Benjamin
is
going
to
remain
on
the
project
in
various
aspects.
I
would
feel
lost
without
some
of
the
good
leadership
we
have
here
all
right
Amir,
it
doesn't
sound
like
you
are
actually
a
new
person
but
I'm
going
to
wait.
A
A
few
minutes
see
if
anybody
else
shows
up
and
discuss
fun,
newcomer
topics
so
we'll
move
on
to
open
discussion
which
we
just
began
with
chair,
updates,
Brian
McQueen
here
I
work
at
LinkedIn
I'm,
the
new
chair
of
this
one
of
the
chairs
of
working
with
Michelle
and
I.
Think
Brady
Pratt
is
probably
one
of
them
too,
and
I
find
that
subject
to
be
not
awesome
and
interesting.
So
I'll
just
move
on
by.
A
We
have
an
issue
here
which
looks
really
interesting
and
I
hope
somebody
will
talk
about
it
because
it
also
doesn't
sound
simple
set
up
periodic
scalability
CI
tests
and
AWS.
That
sounds
like
a
really
fun
project.
Is
anybody
here
know
what's
going
on
with
this?
One
I
thought
so
go
met
your
mom
good
I.
B
Think
this
one
might
actually
be
I
think
this
might
be
bumped
off
our
agenda
actually,
and
we
might
just
have
the
chair
update.
We,
there
was
a
pretty
Lively
conversation
in
scalability
end
of
last
week.
Their
meetings
are
Thursday
the
other
other
week
from
us.
So
we
met
pretty
recently
to
discuss
this
and
there
were
some
representatives
from
Kate's,
infra
and
testing
to
help
discuss
that
so
I
think
we
have
a
path
forward,
I'm,
not
sure
they
had
any
further
questions.
A
All
right,
that's
that's
fine,
and
if
we
run
out
of
material
we'll
just
shut
it
down
and
folks
can
go,
join
Sig
node,
which
is
always
interesting.
But
let
me
take
a
look
at
the
agenda
because
there
is
something
else:
I
wanted
to
go
over
with
y'all
Note
Taker
you're,
going
to
indicate
that
we're
yeah.
Thank
you.
A
A
First
I'll
talk
for
a
minute,
which
is
that
I
was
returning
to
my
hobby
of
trying
to
make
tests
that
are
red.
Look
green,
so
I
went
over
to
the
test
grid
this
weekend,
I'm
going
to
put
a
link,
but
in
fact
you
can
see
it.
If
you
go
to
the
top
of
the
chat
room,
Sig
testing,
the
real
slack
Channel,
there
are
some
links
up
there
at
the
top,
one
of
which
is
test
grid.
A
So
I
went
clicking
around
in
the
test
grid
on
Sunday
and
we'll
see
how
well
sharing
works.
If
it
doesn't
work,
that's
fine,
I'll,
just
talk
my
way
through
it,
I
was
looking
for
a
particular
flaky
test
and
when
I
clicked
on
test
grid,
I
saw
a
large
number
of
things.
A
vast
Suave
of
the
test
grid
had
turned
red.
A
A
I
looked
at
this
thing,
it's
supposed
to
be
all
green
like
this
and
I
was
expecting
to
find
a
little
something
that
was
a
flaky
test,
sporadic
Reds,
but
here's
what
I
spotted
and
if
you
click
over
to
this
one
here
by
the
way,
you're
looking
at
the
test
grid
here
with
the
links
are
in
the
slack
Channel.
This
channel
was
vastly
read
this
particular
tab.
Very
scary.
Looking
I
did
my
best
to
gather
some
data.
A
I'll
even
show
you
very
briefly
about
a
couple
of
things
you
can
do
to
gather
data
when
you're
looking
at
test
failures.
I
went
clicking
through
on
some
of
these
things
that
take
you
to
some
of
the
other
familiar
test
exploration
tools
clicking
through
you
get
to
details
here
that
show
you
test
failure,
data
very
useful
stuff.
A
There
were
a
ton
of
C
group
related
error
messages
down
here
in
this
chunk
of
code.
This
chunk
of
the
log
files
I
won't
get
into
advanced
debugging
I
just
wanted
to
show
you
that,
with
this
button
up
here,
job
history,
you
can
click
over
here
and
start
seeing
Oh.
This
is
what
it
looked
like
right
about
here.
It
had
turned
red.
It
was
all
green
before
so
it's
very
clear
that
something
broke
at
that
time.
A
I
did
a
little
bit
of
digging
around
in
here
and
I
went
over
to
this
Lac
Channel
for
Sig
testing
said
basically
yeah.
Oh
my
God.
What's
the
matter
everything's
broken,
you
know,
of
course,
I
tried
to
sound,
very
professional
about
it
and
very
quickly.
Somebody
came
in
the
channel
who
had
a
pretty
good
idea.
A
These
are
the
tools
that
you're
going
to
want
to
look
at
for
debugging
and
listen
to
the
triaging
of
tickets,
which
usually
happens
in
a
different
meeting
called
signodeci.
You
can
get
involved
there
to
figure
out
which
tests
are
flaky
and
figure
out.
Debugging
tips
from
the
other
folks,
so
I
think
I
will
stop
I
just
wanted
to
give
you
a
little
intro
to
the
tooling.
There.
C
A
A
C
C
C
A
A
Talk
to
newcomers.
Slack
archives,
remember
to
take
a
look
at
the
top
of
Sig
testing
for
links
to
those
tools
like
the
test
grid
and
there's
another
meeting,
Sig
node
CI,
where
tickets
are
triaged,
including
flaky
tests
and
things
of
that
sort.
You
can
hear
about
that
in
the
signode
channel.
That
really
looks
like
about
it
for
the
meeting
today
and
I.
Don't
see
any
reason
to
carry
on
with
it
I
think
we
should
jump
over
to
Sig
node
and
see
what's
happening
over
there.