Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [glassfish-dev] Fwd: Status of Platform TCK
Hi,

I'm pushing too many things at once now, but my plan is to finish my cleanup on DOL perhaps today, and then FINALLY start with an integration of my "tck runner" to GlassFish build, so we would be able to run those "old" TCK tests locally without any fragile preparations. I can do that now for some TCK parts, but I don't know yet if it works for all. Why I am doing that ...

1) To be able to reproduce any TCK failure locally in few minutes.
2) To have access to the server.log etc. (I am not a TCK committer, so I can't download it and I can't run TCK build on Eclipse's Jenkins).
3) To be able to "validate" ANY version/branch of GF against the TCK
4) Arjan was complaining that he had to manually find and download all results. This would simplify it.
5) Then we can create another GlassFish build on Jenkins (or even on own build server) just for the TCK, which would collect all results automatically..
6) DOL - poor performance, bugs, fragile, generics, IO leaks, tech debt ...

But this all means some work and time, so to give some direct answer ...

1) We discussed it with Arjan, he would like to just update the CCR of M7. It is also a matter of a good feeling of all that effort :-) . But if it is not possible for any reason, we can prepare M8 really quick, just collecting all results is a bit painful process.
2) Web Profile CCR: Yes, but it is not a priority at this moment.

I think Arjan is on holidays now, so take this email rather as some report of what I know at this moment.

David.


On 22. 08. 22 3:21, sawamura.hiroki@xxxxxxxxxxx wrote:
Hi, Arjan, David and others.

The latest TCK results seem to use a nightly build instead of a milestone release.
Updating the Platform CCR* and creating the Web Profile CCR requires creating a new release (like 7.0.0-M8) and running the TCK again, I think.
[*] https://github.com/eclipse-ee4j/jakartaee-platform/issues/514

Do you have time to do a release action?
...or do you have any idea of an easier way?

Kind Regards,
Hiroki

From: glassfish-dev <glassfish-dev-bounces@xxxxxxxxxxx> On Behalf Of Ed Bratt
Sent: Thursday, August 18, 2022 12:09 AM
To: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
Subject: [glassfish-dev] Fwd: Status of Platform TCK

Regarding the status e-mail I sent the Platform team earlier today:
I wanted to just check the current status:
1) Does GlassFish intend to continue to promote the M7 release for the EE 10 Platform ballot? If so, the CCR needs to be updated to reflect the last build (which is, I think, fresh this week and is proposed to be promoted tomorrow (Thursday)). I believe that there have been some changes to GlassFish since that was initially created (probably most for Web Profile but ...  It might be cleaner to just update both Platform and Web Profile versions for the ballot which has yet to start. The decision is yours to make.
2) Does GlassFish intend to submit a CCR for Web Profile? (I believe all the results are looking good, as reported by the TCK team below.)
If there is anything I can do to assist with this, please let me know (I could work on a CCR for Web Profile; I could adjust the Platform CCR with latest TCK updates, if that is desired). I'd need details about the proposed Ballot release(s)-- Their names, location, etc.
Thanks,
-- Ed


-------- Forwarded Message -------- 
Subject: 
Status of Platform TCK
Date: 
Wed, 17 Aug 2022 07:57:30 -0700
From: 
Ed Bratt mailto:ed.bratt@xxxxxxxxxx
To: 
glassfish developer discussions mailto:glassfish-dev@xxxxxxxxxxx

In yesterday's Platform committer team meeting, I volunteered to find the status of the Platform TCK
As of this morning, the proposed final TCK is in the process of validation runs against Eclipse GlassFish. If the build results (EE 10 Platform JDK 11 + JDK 17 and EE 10 Web Profile JDK 11 and JDK 17) all pass as expected, this latest build will be promoted as final candidate. There was a logging issue that was causing test time-outs and that issue appears to be corrected now.
Anyone keen on the gory progress details can follow along by reviewing the pre-ballot checklist progress from the following
• https://github.com/jakartaee/specifications/pull/498#issuecomment-1144500745
• https://github.com/jakartaee/specifications/pull/497#issuecomment-1144500408
Prior to ballot
Concurrency Utilities must release their final TCK for Web Profile. I would recommend their clearest signal of this would be to submit a PR to update the Concurrency Utilities Specification Page
All vendor product releases (final, staged, etc.) must be completed by their respective organizations (we just need the link to their product)
• EE 10 Platform -- https://deploy-preview-498--jakartaee-specifications.netlify.app/specifications/platform/10/ currently lists: GlassFish 7.0.0-M7
• EE 10 Web Profile -- https://deploy-preview-497--jakartaee-specifications.netlify.app/specifications/webprofile/10/ of the PR currently shows TBD
The CCR(s) must be complete and in review (primarily the TCK data must be finalized and the vendor teem must indicate they have completed their processes)
• EE 10 Platform PR for GlassFish 7, M7 points to previous Platform TCK (since the latest is not yet released) and original concurrency TCK
• I don't see a CCR for any web-profile compatible product yet. I know that Eclipse GlassFish is likely to pass. I hope we see a CCR for Web Profile shortly.
The Specification Team (in this case, a representative of this group) must give the go-ahead for the final ballot to start.
-- Ed
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev



-- 
David Matejcek | OmniFish
david.matejcek@xxxxxxxxxxx | +420 777 601 682

Back to the top