►
From YouTube: SunPy Developer Discussion
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
C
B
The
last
word
was
Jack
asking
me
about
adding
some
more
tests
or
making
the
test
a
little
bit
more,
adding
more
coverage
to
the
test,
so
I
did
that
and
I
also.
There
was
one
outstanding
issue
about
that.
Other
code
and
util
and
I
looked,
I
did
a
search
on
their
entire
repo
and
we
don't
use
that
code
anywhere
else
in
the
in
some
pie.
So
I
just
deleted
it.
A
C
C
Okay,
oh
yeah,
it
is
it
ok,
I.
A
B
B
A
B
A
B
It
it
iterates
over
all
of
the
hashes
all
the
files,
and
then
it
makes
sure
to
see
that
there
is
an
actual
wait.
What
is
it
doing?
What
am
I
doing
here
I'm
here
with
my
mix
myself.
B
A
B
A
A
A
B
A
You
do
figure
figure
equals
true
to
self
test.
It
will
also
run
the
figure
tests.
Okay,
basically,
what
this
allows
us
to
do
and
then
also
why
did
in
this
progress
was
added.
A
separate,
build
I
think
did
I.
Do
nothing.
Is
it
did
I?
Yes,
okay,
oh
yes,
and
then
why
did
I
did
a
separate,
build
the
Travis
matrix
which
one's
the
figure
tests?
So
if
the
figure
test
breaks
only
one
element
in
the
Travis
build
files?
Oh
good.
B
It's
basically
just
the
figure
tests
and
nothing
else.
It's
just
the
figures,
so
you
just
have
to
manually
copy
the
figures
in
know
what
I
was
thinking
was
that
eventually
we
could
just
have
in
on
a
fail.
We
could
just
create
the
URL.
For
you
and
say
you
know,
this
failed,
go
check
it
and
here's
the
URL
and
then
you
can
compare
your
figure
with
the
one.
That's
online.
A
A
B
B
C
And
I
did
three
different
pull
request
for
different
hashes
that
we
have
happened
there,
but
I
could
recover.
So
you
can
go
in
the
history
of
those
figures
and
see
how
have
change
so
instead
of
doing
just
for
the
last
one.
Just
for
the
sake
of
comparison
of
how
that
will
work
in
the
future.
I
added
three
different
versions:
not
the
akhand
environment
list
of
the
packages
installed
just
to
check
the
version
of
the
different
packages
I've
if
there's
a
new
hast.
C
If,
for
some
reason
the
tests
are
starting
to
fail
in
the
new
the
new
run,
and
we
know
why
we
can
check,
we
can
try
to
run
an
environment
with
the
same
versions
and
see
whether
it
is
something
that
travis
has
updating
without
letting
us
know
or
whether
it's
m
and
something
different
yeah
and
I
guess
I
for
all
the
files.
I
have
had
3
different
versions
that
you
can
go
into
different,
commit
and
see
like
how
much
they
hashes
change
it
or
something.