►
From YouTube: SIG-Testing Biweekly Meeting for 20230321
Description
Sig-Testing Biweekly Meeting for 20230321
A
A
B
Yeah,
can
you
hear
me
yeah
yeah,
hi,
I'm,
arunima
I
am
from
India
I
have
around
four
year
experience
in
working
as
a
web
developer,
and
this
is
my
first
time
trying
to
contribute
to
a
open
source
project.
So
this
is
very
new
to
me.
So
that's
the
reason
why
I've
started
I
want
to
understand
how
kubernetes
work
and
the
code
base
so
I
want
to
start
with
testing
and
then
story,
work
going
way
upwards
towards
development,
and
so
yeah,
that's
more
or
less
about
me.
A
The
other
thing
is
I.
Think
people
try
to
regularly
like
curate
and
tag
those
when
triage,
but
we
could
always
use
like
a
regular
look
over
from
folks
more
experience
in
the
repo
to
see
if
there's
any
other
things
that,
like
either
haven't
been
recorded
or
some
things.
That
would
actually
be
good
as
help
wanted
a
good
first
issue,
but
haven't
been
tagged
as
such.
A
Yeah,
the
other
thing
that
might
be
useful
is,
if
you
want
to
take
a
look
back
at
some
of
the
past
meeting,
notes,
I'm
sure
or
in
the
stick
testing
Channel
in
slack
things
come
up
here
or
there
fairly
often
I-
think
that
our
active
and
or
could
use
help
a
lot
of
the
time
just
because
we
mentioned
it
here
doesn't
mean
it's
solved.
Of
course,.
A
All
right,
let's
go
ahead
and
leave
it
that
and
then
yeah
for
the
agenda
today.
I
think
we
only
have
the
one
thing,
but
if
there
is
anything
else
that
folks
want
to
talk
about,
please
feel
free
to
start
adding
it
on
the
meeting
notes
as
well
so
yeah.
The
annual
report
for
Sig
testing
is
being
drafted
right
now.
A
There
is
a
open
dock
that
anybody
can
contribute
to
that
is
linked
here
and
basically,
just
has
like
a
a
bunch
of
stuff
that
people
have
put
in
from
either
work,
they've
done
or
past
meeting
notes
or
stuff
like
that.
If
there's
anything
that
you
see,
that
was
done
in
2022
in
the
Sig
testing
area
that
should
be
represented
and
hasn't
been.
A
So
I
know
that
there
are
probably
some
parts
of
like
selflessly
testing
owns
or
helps
out
with
that
almost
certainly
could
use
more
hands
regularly
like
contributing.
So
if
you
have
any
specifics
to
points
out
there,
please
add
it
to
the
draft
I
think
the
PR
will
be
opened
for
official
review
on
the
or
by
the
24th
and
then
will
be
reviewed
like
a
week
later.
Something
like
that
so
yeah
by
the
end
of
the
week
would
be
great
yeah.
A
D
D
A
A
I'll,
let
that
handle
yeah,
the
the
main
thing
I
could
think
of
would
be
like
for
starting
debugging,
just
like
being
able
to
get
the
logs
from
it
like
I,
because
it's
a
privately
run,
one
I
don't
think
I
can
like
have
access
to
it,
for
instance,
but
there
should
be
like
info
logs
around
what
action
was
taken
on
the
pr,
for
instance,
which
is
where
I
would
start.
It's
just
searching
the
pr
number
and
then
like
filtering
for
any
of
the
useful
components
of
proud
that
probably
took
action.
A
D
So
we
we
kind
of
did
that
and
Trend
and
that's
why
we
basically
got
error
message
not
found
which
is
not
really
meaningful
and
I.
Try
to
check
brow
card
base
and
I
can't
find
anything,
because
we
went
to
all
the
components
involved
in
the
merge
process,
which
is
basically
tight
and
oops.
We
didn't
find
anything
except
the
error
message,
so
I'm
trying
to
figure
out
how
to
can
how
I
can
debug
this.