Re: [glassfish-dev] GlassFish 6.0.0 release still on track?

[Lukas Jungmann <lukas.jungmann@xxxxxxxxxx>]

On 12/8/20 12:10 PM, arjan tijms wrote:
> Hi,
>
> On Tue, Dec 8, 2020 at 12:02 PM Lukas Jungmann 
> <lukas.jungmann@xxxxxxxxxx <mailto:lukas.jungmann@xxxxxxxxxx>> wrote:
>
>
>      > Unfortunately there are regressions:
>      >
>      > Test Result (8 failures / +8)
>
>     these are fixed already in the current binary (there was a EL 3.0
>     respin
>     about an hour ago due to this).
>
>
> Thanks, just to be 100% sure, with the current binary you mean this one, 
> right?
>
> https://jakarta.oss.sonatype.org/content/repositories/staging/org/eclipse/persistence/eclipselink/3.0.0/ 
> <https://urldefense.com/v3/__https://jakarta.oss.sonatype.org/content/repositories/staging/org/eclipse/persistence/eclipselink/3.0.0/__;!!GqivPVa7Brio!Ouc3B-nfeNH9ccOwUS0AfsCVd3yZtbKmC5GeubwbgGklnOOD3zZY2gWL0-vVGp0ZjEs$>

yes, here is the test run: 
https://ci.eclipse.org/jpa/job/TCK_jakarta_JPA_run/17/console (still 
some 450 tests to go but the one failing already passed)

once it ends and passes, that binary will be promoted to central


thanks,
--lukas

>      >
>     com.sun.ts.tests.securityapi.idstore.database.invalidpriorityuseforexpr.Client.testAnnotationDBIDStore_invalidpriorityuseforexpr
>      >
>     com.sun.ts.tests.securityapi.idstore.database.multi.Client.testAnnotationDBIDStore_multi_withLdap
>
>
>   I'll take a look at these ones. Too bad the TCK doesn't show the 
> actual exception there, but this is technically quite difficult to do.