On 5/24/22 10:57, Jiri Vanek wrote: > > > On 5/23/22 20:40, Kevin Fenzi wrote: >> So, just replying here since this is a nice monster of a thread. ;( >> >> First, just to clear up some previous coments, shim does build against >> the oldest stable Fedora in koji and then is manually tagged into newer >> ones. This is not at all a good process. It only gets a bodhi update for >> the one release (and sometimes not even that), so it never gets good >> testing. It requires manual intervention from releng each time there's >> an update. I think the only reason this has kept going is that shim is >> very small and simple and updates rarely. If we need to do this for tons >> of openjdk updates, we really should revisit the process, although I am >> not sure how to make it more open to testing and less a burden on >> releng. ;( > > Thanx for bringing up additional details! >> >> Next, My understanding of the current process for openjdks (openjdki?): >> >> for each openjdk: >> >> Build dyanmically linking against system libraries in all fedoras. >> Submit to TCK and wait for them all to process. >> Fix any TCK failures and repeat >> Once there's no failures, push the builds to updates >> >> Is that right? And keeping the dynamic builds passing is taking more >> cycles than you have to give for the number of jdks? > > super correct. > >> >> What about the possibility of adding CI _upstream_ to test against the >> dynamic version? Then TCK failures would be caught upstream and not >> downstream where it's a lot of work for you to fix? > > We are testing also upstream. note that RH is maintainer of ojdk 11 and 8, so we have to. But that is much easier, as the usptream is static within intree libraries. And we have to run also for 17 and 18/19 as we need this reference run, > to be sure that downstream is guilty, not vanilla jdk. Thus we test the (source x build) just once. And we can test the binary on some known system where we always pass. > But in downstream, new issues usually appear due to the dynamic linking and nature of system where only it can be installed. Also for dowstram, each sources are built N times, so N times tested in thsoe N systems - usually each with its > psecific failures. Kevin’s suggestion is for upstream to test dynamic builds, not just static ones, in its CI. That means that if the dynamic build breaks, it would be upstream’s problem. In other words: Instead of shipping a static JDK in Fedora, make the dynamic JDK a first-class citizen upstream. -- Sincerely, Demi Marie Obenour (she/her/hers) _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
