►
From YouTube: TCK call #11 (May 11, 2022)
Description
May 11, 2022 Jakarta EE Platform TCK call #11. Minutes can be viewed via https://docs.google.com/document/d/1V1dDLJkd14EDRMPeuI0VzPtU4Lbli8FFBd1pLDLlOrY/edit#bookmark=kix.294kzg90os0n
A
A
A
So,
of
course,
the
general
topic
is
ee,
10
tck,
the
first
pull
requests.
We
wanted
to
go
over,
let's
see
well
actually
just
on
on
the
on
ee
10
tck.
Over
the
past
few
weeks,
we've
been
drilling
into
all
kinds
of
issues
on
different
projects,
issue,
trackers
and
mailing
lists,
and
one
thing
that
came
out
of
discussion
yesterday.
I
I
think
at
the
platform
call
or
wherever
I've
been
talking
to
scott
stock.
Was
that
yeah?
We,
you
know
we
should
have
yeah.
A
We
should
create
platform
tck
issues
for
each
of
the
failures,
so
that
we
can
have
a
clear
understanding
in
the
platform
tck
of
where
the
other
discussions
are
occurring
and
what's
going
on
with
the
statuses
instead
of
trying.
Yes,
we
don't
have
to
pull
it
together
from
multiple
sources,
but
that's
you
know,
that's
that's
not
necessarily
where
the
bugs
will
be
fixed,
but
but
you
know
for
our
own
sanity,
you
know,
so
we
can
track
more
effectively
and
for
my
sanity
anyways
for
I'm
trying
to
recall
everything.
B
Be
yeah
helpful.
The
other
thing
is,
I
think,
like
the
so
the
the
962
pull
by
it
looks
like
so.
I
created
several
questions
based
on
looking
at
that,
because
I'm
I'm
not
that
familiar
with
the
tck
structure,
so
I
just
want
to
try
and
get
oriented
on
that
and
try
to
help
other
people
come
on
board
and
how
we
can
parallelize
some
of
these
issues.
But
that
looks
like
that
spin.
B
That
needs
to
be
done
for
a
bunch
of
different
tests.
So,
like
one
of
the
think
one
of
the
questions
down
there
is
looking
at
the
change
you
made
for
the
egb
light
jsf
vehicle
and
then
how
that
applies
in
that
mappings
file.
It
looks
like
that
work
needs
to
be
done
for
several
different
package
test
packages.
B
A
Following
yeah,
I
did,
I
did
look
myself
at
one
at
one
of
one
of
those
parts,
but
but
yeah
it's
been
a
big
challenge
over
the
last
few
years.
You
know,
do
we
you
know,
do
we
seek
to
understand?
You
know
those
kinds
of
things
or
do
we?
You
know
you
know
eliminate
them,
and
certainly
if
we
understand
them
that
that's
all
the
better
and.
A
You
can't
I
mean
you,
I
I
know
from
the
ant
command
line.
I
I
don't
know
if
we
have
it
in
the
glass
fish,
tck
portent
kit,
but
knowing
the
in
in
the
tck
itself,
you,
you
certainly
can
run
individual
tests.
I
do
with
wildfly
when
I,
you
know,
run
tc
tck
tests
locally
with
script,
and
we,
you
know
with
bash
script,
and
we
have
set
up
to
run.
You
know
to
run
that
you
know
we,
you
know
we
we
can,
for
the
most
part,
run
individual
tests.
A
You
know
just
you
know
like
there's
at
like
there's,
basically
like
two
like
there's
two
levels
of
doing
that,
and
one
is
you
id.
You
know
I
I
know
for
like
with
glassfish.
You
cannot
identify
and
identify
the
test
folder
level
with
what
glassfish
tck
important
kit
supports,
currently
with
the
scripting,
and
that
gets
you
to
run
all
the
tests
in
that
test
group
or
test
folder,
which
is
close
closer
than
running
all
the
tests
from
the
root.
A
It's
one
one
part,
but
you,
but
you
can
also.
You
can
also
specify
the
include
the
the
test
name
as
well.
I
don't
know
if
I
don't
know
if
that
works
with
glass
fish,
I've
never
tried.
You
know
tried
that
myself,
I've
only
done
it
with
wildfly
and
and
brian
could
probably
speak
to
open
liberty
yeah.
So
I
was
gonna
say:
that's,
that's
only
a
statement
to
the
test
class
level
right
you,
I
don't
believe,
there's
a
hook
to
do.
A
Okay,
so
so
let
me
I'll
I'll
I'll
I'll,
just
post
and
I'll
just
paste
an
example
into
the
agenda
of
how
you
know
oops
of
how
I,
how
yeah,
if
it
were
with
wildfly,
how
I
would
you
know
how
I
would
do
it
so
with
with
wildfly
and
these
two
don't
necessarily
these
two
settings
test,
folder
and
test
name,
don't
go
with
each
other,
but
I
just
happened
to
you
know,
pull
it
out
of.
You
know
out.
C
A
Of
yeah
in
yeah
out
of
history-
and
you
know
he's
you
know,
he's
easy
enough
to
to
recall
these
two.
But
what
what
I
see
here
is
I'm
identifying
the
the
test
group
to
run,
which
is
fine
and
I'm
actually
identifying
the
individual
test,
including
you
know
the
the
vehicle
to
run
because
it's
like
for
the
json
provider
tests,
one,
that's
so
that's
a
so
that's
something
I
am
doing,
and
then
you
know
it's
it's
basically
in
the
scripting,
I'm
just
passing
what
ant
expects.
A
A
B
A
A
A
So
so,
let's
see
so
so
yeah
the
the
test.
Oh
yeah,
I
should
pull
it.
Let
me
just
do
one
other
one
and
well.
The
test,
folder,
is
what
we
change
yeah.
We
change
into
the
test
folder,
basically,
and
that
that's
kind
of
that's
pretty
standard.
That's
what
glass
fish
is
doing
every
that's
the
only
way
you
do
it.
You
basically
change
into
that
test
folder,
but
from
there
we're
invoking
and
with
the
dash
d
test
equals
and
then
that
test
name
and
at
the
ant
level.
A
You
know:
that's
that's
where
yeah
that
you
know
that.
That's
how
it's
handled
so
made
the
glass
fish
tck
could,
could
you
know
yeah,
you
know.
Could
you
know,
could
support
that
and
you
know
open
liberty.
Can
you
know,
can
now
I
I
guess,
there's
like
law
there's
a
lot
of
you
know
things
that
that
are
just
in
the
ant
script
and
that
aren't
necessarily
described,
but
you
just
come
across
them
and
then
you
use
them
so
yeah
yeah!
That's
that's!
C
C
Yeah,
I
haven't
done
anything
a
single
test
for
like
for
some
time.
Like
mostly,
I
have
been
running
the
suits,
so
why
I
think
in
saw
the
entire
suit
for
some
time,
so
I
don't
exactly
remember
how
to
run
the
single
test,
but
from
the
wiki.
I
think
we
we
could
make
use
of
these
run
script
that
we
have
in
docker
folder
I
have
sent.
C
This
is
pro.
I
think
this
is
is
still
valid.
Like
the.
I
have
pasted
that
in
the
comments,
so
we
could
use
the
run.
Script
run,
jakarta,
tck,
dot,
sh
and
pass
the
suit
name.
If
we
have
a
vehicle,
we
do
like
underscore
vehicle,
but
this
is
when
we
have
the
bundle
available
when,
when
we
have
the
platform
pca
bundle
available
and
extracted
so
yeah
yeah,
I
could.
I
could
check
in
in
my
directories
like
how
exactly
we
run
a
single
test
yeah.
A
C
A
C
B
A
A
A
That's
just
an
example
there's,
but
there's
other
like
there's,
there's
all
there's
all
different
test,
folders
that
each
to
have
their
own
special
things
that
you
have
to
include
when
you
do
rebuild
them,
but
you
can
you
can
kind
of
make
changes
on
the
fly
like
that
and
then,
of
course
you
know
I
could
like
for
the
for
the
run
ops
changes.
I
was
trying
to
do
with
glass
fish.
I
I
just
changed
the
xml
files
on
the
fly
and
just
was
trying
different
things.
A
You
know,
instead
of
just
you
know,
instead
of
rebuilding
the
platform
tck,
I
would
just
make
changes
to
a
few
xml
files
and
and
test
again,
so
it's
kind
of
not
really
quite
the
same
thing,
but
so
I
don't
know
if
doing
the
ant
build
applies
to
all
kinds
of
changes
that
you'd
want
to
make.
But
that's
you
know
that
you
know
that's.
You
know
that's
one
of
them
that
can
can
be
used
as
well.
A
C
A
A
Okay,
yep
yeah
yeah
you
have
to
you
have
to
we
add
we
get
to
set
the
jdk
variable.
All
you
know
also
should
probably
make
that
clear,
clearer.
But
basically
this
is
all
you
have
to
do
you
point.
You
know
you,
you
point
to
the
you
know
the
glass
fish
build
and
it's
good.
The
the
run
script
is
gonna
is
gonna,
you
know,
is
gonna
download,
glass,
fish,
there's
a
way
to
point
heading
system,
one
as
well.
A
The
latest
stage
you
know
one
that
we've
built
from
the
from
you
know
from
from
ci
as
well,
and
it's
just
you
know.
This
is
just
like
a
check
to
see
like
I,
I
don't
have
a
permanent
place.
I
just
do
it
in
my
temp
folder,
I
don't
I
don't
run.
I
don't
do
it.
You
know
to
run,
run
it
locally
with
glass
fish.
You
know
too
often,
but
this
is
pretty
close
to
a
work,
and
you
know
example.
B
Okay,
that's
good,
and
then
so
when
I
was
looking
at
your
pull
requests
all
in
the
962
and
just
trying
to
understand
what
that
ts
vehicles
like
smell
does
so,
basically,
that's
for
a
given
vehicle
that
that
file
like
what
they
call
it
task
and
test
definition
that
defines
how
that
vehicle's
archive
is
built.
Is
that
correct.
A
B
C
B
C
C
Yeah,
I
I
think
it
would
be
easier
like,
since
we
already
know
what
kind
of
change
we
need
to
make.
Also,
we
need
to
separate
ejb,
like
json
vehicle
run
from
the
like
the
same
folder.
The
same
client
will
be
used
to
run
like
multiple
vehicles,
including
jb,
light
jsf,
so
we
won't
be
able
to
use
the
client
that
is
used
for
ejv,
like
jsf,
so
we'll
have
to
separate
like
like.
I
did
like.
I
used
the
data
plan.
Yes,
so
that's
something
we
need
to.
B
C
A
C
A
It
works,
it
works
for
me
and
alwyn
and
guru,
but
you
know,
maybe
we
could
you
know,
maybe
a
pull
request.
You
know
option
would
be
yeah
enough.
I
don't
know
what
others
think
about
that
if,
if
that
would
be
a
good
alternative
to
to
that,
so
so
we
have
kind
of
like
these
personal
tck
run
runner
jobs.
C
A
B
A
C
A
A
Yeah
yeah
I
mean
I
I
I
yeah
it
sounds
like
I
mean
it
would
just
be
like
a
simple
field
and
then
yeah
you
just
yeah.
Given
the
poll
request
link
I've,
never
I've
never
done
it,
but
I
I
know
I
do
it
all
the
time
locally.
I
you
know
I
you
know
fetch,
you
know
fetch.
You
know,
take
the
pull
request
and
get
the
branch
info
and
yeah.
I
know
there's
a
way
to
do
it
and
I've
seen
others
do
it.
I
just
never
have
done
it
myself,
but
but
it
shouldn't
be.
A
Here,
who
doesn't
have
the
setup
yet-
and
you
know
scott
who
is
you
know
now
a
platform
tck
committer
welcome
and
doesn't
have
the
special
job,
and
so
we
really
have
a
option
here
to
set
up
the
pull
request.
Your
runner,
I
think,
would
be
you
know-
might
be
less
labor-intensive
than
every
committer
setting
up
a
special
job,
but.
A
A
C
A
B
A
B
A
B
A
A
A
You
know
you
know
proper
managed
beans
which
I
you
know
you
know
the
different
ee
implementation
support
in
use
in
the
ejb.
You
know
30
tests
and
I
kind
of
yeah
yeah.
I
I
thought
those
were
being
you
know
in
in
play
and
with
this
all,
but
it's
it's
all
you
know
it's
actually
so
we're
still
as
al
one
said
it.
You
know
it's
it's
just
you
know,
jakarta
faces,
annotation
manage
property,
it's
all
you
know
so
fake.
You
know
faces
it's
all
still
in
you
know
faces
stuff,
it's
not!
A
B
B
So
I
think,
like
what
I'm
going
to
do
is
take
one
of
the
other
egb
light
tests
and
just
try
and
follow
what
alwyn
did
and
create
a
pr
on
that.
Just
to
verify
that
I
understand
what
the
issues
are
and
then,
like
I
said,
if
that
makes,
if
that
looks
good
makes
sense,
then
we
can
just
create
an
issue
for
all
the
other
sub
packages
and
assign
them
or
let
people
pick
them
up.
B
A
B
A
A
C
A
C
A
A
B
A
A
A
B
A
C
A
C
C
A
C
B
Okay,
all
right!
Well,
okay,
I
think
that's,
that's
a
good!
It's
a
good
starting
point
for
me.
So
I'll,
create
an
issue,
create
an
initial
pr
and
verify
the
direction
that
we
think
we
need
to
take
following
all
wins,
962
pr,
so
we
would
spin
that
off
on
the
remaining
tests
that
that's
the
that's
by
far
the
majority
of
the
failures
it
looks
like.
B
A
A
C
C
A
B
A
A
A
I
and
I
I
I
didn't
yeah-
I
didn't
quite
understand
it
until
you
know
you
know
scott
and
allen
just
discussed
it.
I
didn't
get
that
we
had.
I
I
saw
that
alwyn
was
doing
it
in
in
a
particular.
You
know
we
have
a
pull
request
that
looks
ready
to
merge
for
the
particular,
for
you
know,
test
folder
I
didn't
yeah.
I
didn't
know
where,
yet
that
we
needed
to
repeat
that,
but
that
yeah,
that
makes
sense
so
yeah.
B
B
B
Actually
so
what
I
was
going
to
do
was
create
one
one
main
issue
that
described
the
packages
that
it
looks
like.
We
need
to
update
some
performance,
the
starting
point
to
verify
that
I'll.
We
can
verify
that
and
then
create
sub
issues
for
each
of
the
the
packages
and,
like
you
said,
we
can
create
those
up
to
people
who
are
not
duplicating
works.
A
A
B
B
C
A
A
You
know
that
you
know
processed
glass
fish.
You
know
you
know
we'll
need
a
way
to
set
addition.
You
know
the
additional
jdk
options
that
they've
that
are
specified
in
tia.
You
know
ts
jte,
that
the
pull
you
know
the
pull
requests
we
added
for
the
other
test.
You
know
you
know
to
use
for
that
test
process.
Also,
I
don't
really.
A
I
don't
really
like
it,
but
I
don't
yeah
glass
fish
is
like
the
only
one
that
has
to
run
ejb
embedded
and
it's
kind
of
you
know
it
has
to
be
in
the
test
process.
So
yeah
you
know
it's
just
going
to
have
to
be.
You
know
well
to
be
careful
that
it
doesn't
intrude
on
other
testing
for
other.
You
know
tests
in
some
way.
I
think
but
you're
not
sure
yet
about
that,
but
we'll
you.
C
A
A
B
A
B
A
A
So
it's
you
know,
it's
it's
a
work
in
progress,
but
it's
it's
I
mean
you
guys
are
doing
all
the
transformation
work
out
here
and
it's
it's
not
a
small
piece
of
work
to
adapt
to
all
of
that.
Internally
too.
So
I
I
wish
I
could
help
more
in
the
work
that
you
guys
are
doing,
but
we
don't
have
a
lot
of
people
here
in
liberty
working
on
it,
so
I'm
I'm
mostly
consumed
responding
to
the
changes.
If
you
know
what
I
mean.