►
From YouTube: Node.js Build WG meeting - Jan 8 2019
Description
A
So
welcome
to
the
January
8
2019
nodejs
community
benchmarking
meeting
it'll
probably
be
held
fairly
or
sorry
build
yes.
Certainly
a
build
meeting
it'll
probably
be
fairly
short,
because
it's
just
myself
in
Raphael,
but
we
thought
we'd
quickly
walk
through
the
issues
on
the
agenda
just
because
we
were
starting
to
do
that
anyway.
So
let
me
bring
that
back.
A
And
that
way
at
least
anybody
who
did
want
to
try
to
tune
in
to
watch
can
get
a
quick
update.
So
I
guess
the
first
one
is
just
what
was
on
the
agenda,
but
it
has
landed
so
Trish
Patel
has
been
added
to
the
members
and
he
was
on
boarded
by
Jo
earlier
I
think
late
last
week.
So
that's
great
welcome
to
riche,
oh
and
rich.
Let
me
just
promote
rich
there.
You
go.
A
C
A
Just
pasting
it
into
the
chat
here
for
people,
okay,
sure
so
right
so
Dreyfuss
onboard
with
jello
last
week
and
so
I
think
that
one's
more
awareness
than
anything
else,
the
next
one
is
issue.
1631
witches
can't
make
lint
py
python
equals
Python
three
be
mandatory
in
Jenkins
tests,
so
I
think
Raphael.
You
were
mentioning
that
you're
up
to
speed
on
that
one.
D
The
issue
there
so
there's
been
work
on
an
ansible
script
that
will
set
up
Python
3
on
a
machine
and
we
will
either
replace
one
of
the
current
limiters
with
that
machine
and
run
lint
off
and
bitin
2
&,
5,
&,
3,
okay
and
that's
about
it.
Oh
first
of
all.
What's
missing
is
that
I
think
there
is
a
small
gap
of
files
in
the
node
repository
which
are
not
Python,
3,
lint
free,
but
once
we
get
that
we'll
obviously
turn
on
the
linter,
so
it
doesn't
regress
right.
A
D
A
C
A
C
A
D
D
A
I
mean
we
have
an
action
plan.
The
first
one
is
George
is
working
on
the
third
machine,
which
was
a
pre
with
the
this
issue.
Just
so
that
we'd
go
from
two
to
three
and
we're
and
our
real
solution
is
we
have
like
a
honking
big
machine.
I,
don't
know
it's
like
hundreds
of
course,
which
were
in
the
which
we
had
but
weren't
using
enough.
So
we,
you
know
I,
think
we
have
the
okay
to
donate,
that
to
OSU,
where
we
have
these
other
ones
hosted.
C
D
A
Just
there's
lots
of
checks
and
balances
so,
and
actually
part
of
it
is
just
us
working
with
OSU
as
well.
In
terms
of
you
know,
getting
getting
them
ready
to
accept
the
machines
and
doing
whatever
pre-configure
we
can.
So
it's
it's
a
combination
of
all
those
things.
George
George
was
like
hoping
for
February
I,
think
that
might
be
optimistic,
but
I'd
be
very
happy
if
we
get
it
there
for
them.
A
We've
got
a
what
we.
Yes,
we
have
a
plan,
but
we
just
need
to
execute
on
okay,
so
the
next
one
is
request
for
elevated
privileges,
1337
I
think
rod.
Rod
still
had
the
action
to
you
know:
try
and
tease
out
different
levels.
I,
don't
think
you
know.
We
don't
have
an
update
on
that,
and
it's
of
course,
if
anybody
else
has
time
to
work
on
that.
That
would
be
good
too.
A
I'm
just
gonna
say
no
update
this
time
use
foundation,
resources
to
support
build
so
that
one
we
had
a
bit
of
a
discussion
last
week
and
I'd
have
to
go
back
and
look
at
the
notes,
but
we
did
have
some
other
ideas
and
stuff
that
we
were
going
to
talk
about.
I.
Think
rod
took
the
action
to
comment
in
that
issue
with
some
of
the
the
other
things
that
we
were
gonna
explore.
I
remember.
D
A
A
A
B
I'm
not
sure
this
is
a
gender
worthy,
but
it
probably
is
so.
We
currently
have
a
nightly
job
that
runs
benchmark
tests
and
internet
calls
on
a
Linux
machine.
I
would
like
to
add
pummel
test
to
that
list
and
I
think
I
know
the
process,
but
I
would
love
to
have
somebody
watch
over
my
shoulder,
and
just
you
know
like
virtually,
and
you
know
just
kind
of
like
you
know
pair
on
it
basically
to
make
sure
I'm,
not
you
know,
I'm,
not
forgetting
to
document
something
like
that.
B
The
second
part
of
that
can't
can't
do
that
until
a
bunch
of
Porticus
I
have
up
and
landed,
but
it
looks
like
all
in
the
next
48
hours.
So
the
second
thing
I
want
to
do,
though,
is
I,
propose
that
we
add
a
second
nightly
job
to
run
the
pummel,
Internet
and
benchmark
test,
but
that'd
be
on
Windows,
because
that
is
the
most
likely
other.
D
D
B
D
C
A
D
A
D
C
B
D
A
B
B
C
A
B
Then
people
cuz,
like
people
are
already
complaining
that
you
know,
like
you
know,
there's
there's
a
few
develop
regular
contributors
who
are
not
happy
about
how
slow
the
tests
all
right.
So
my
plan
is
to
move
a
bunch
in
to
pummel.
Actually,
I
have
a
PR
for
that.
Some
of
the
tests
to
take
20
or
30
seconds,
move
them
into
pummel
and
I.
B
Don't
want
to
do
that
until
we're
actually
running
pummel
NCI,
because
otherwise,
because
the
thing
about
the
thing
that
I'm
finding
as
I'm
fixing
them
one
by
one,
is
that
nobody
runs
to
the
pummel
test
like
a
bunch
of
these
have
been
broken
since,
since
you
know
right
when
I
fixed,
it
worked
in
node
0.12,
but
not
in
node.
For.