Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.java > #12623

jtreg 7 vs. jtreg6 vs. testng vs. openjdk-8 (was Re: OpenJDK package - JTREG 7.1)

Show key headers only | View raw

Hi Vladimir,

>Sorry for the late reply, but I have realized that there might be an
>issue with adopting jtreg6 for Java 8 testing.
>
>Jtreg 6 requires testng 7.3[1] and Jtreg 5 uses 6.9.5[2]. The current
>jtreg6 package uses 6.9.5 making it suitable for Java 8 testing but
>not so much for 11 and up. If testng is upgraded to 7.5 it will be
>still binary compatible, but there will be new regressions due to API

OK, good to know. However, let’s translate this, thinking in
upstream versions/dependencies, to Debian now.

Debian has testng 6.9.12 in “all” releases (jessie-backports and up).
src:openjdk-8 testing works with that, so we can use this for the
jessie and stretch ELTS uploads. As long as pochu doesn’t update
testng in either, we’re fine, jtreg6 or not.

When testng 7.3 will be uploaded to Debian (not before the release
of bookworm), then openjdk-8 in sid should either use jtreg 5 (which
doesn’t mix with Emmanuel’s plans to update jtreg to 7) or will have
extra test failures in trixie/sid.

The jtreg update hasn’t happened yet, and also will not occur before
the bookworm release, so there’s ample time to consider this.

Honestly, openjdk-8 isn’t officially part of trixie (although people
may very well build it for it) and the sid one is not “officially
supported”, the jessie/stretch ELTS builds are our primary deliverables,
so I can live with the extra test failures in sid (as long as they still
run at all). As for *buntu, they seem to be hiding the openjdk-8 updates
in paid-for subscriptions so I can ignore what they do, anyway.

stretch-ELTS is EOL on 2027-06-30 so we need to somehow be able to keep
openjdk-8 around and supported-ish until then, but if it doesn’t become
possible in sid any more, it’ll end up being an ELTS-only problem.

I don’t know whether there are any more bootstrapping things that could
benefit from openjdk-8 in sid currently or planned. However once it’s
gone it’s very unlikelt it’s possible to bring it back again any more,
especially should the target class version be bumped. I’m not sure for
how long -target/-release 8 will be state of the art in either Debian
or otherwhere (Maven Central), but it seems to be very long-lived. (We
have customers still using it as JRE so I check whether things work on
it, except I’m not currently in a Java project at work.)

bye,
//mirabilos
-- 
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

                        ****************************************************
/⁀\ The UTF-8 Ribbon
╲ ╱ Campaign against      Mit dem tarent-Newsletter nichts mehr verpassen:
 ╳  HTML eMail! Also,     https://www.tarent.de/newsletter
╱ ╲ header encryption!
                        ****************************************************

Back to linux.debian.maint.java | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-02 00:50 +0100
  Re: OpenJDK package - JTREG 7.1 Thorsten Glaser <t.glaser@tarent.de> - 2023-03-02 01:40 +0100
    Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-02 02:00 +0100
      Re: OpenJDK package - JTREG 7.1 Thorsten Glaser <t.glaser@tarent.de> - 2023-03-02 02:10 +0100
        Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-03 02:30 +0100
          Re: OpenJDK package - JTREG 7.1 Thorsten Glaser <t.glaser@tarent.de> - 2023-03-03 04:00 +0100
            Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-14 03:50 +0100
              Re: OpenJDK package - JTREG 7.1 Thorsten Glaser <t.glaser@tarent.de> - 2023-03-14 10:40 +0100
                Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-14 20:00 +0100
                Re: OpenJDK package - JTREG 7.1 Thorsten Glaser <t.glaser@tarent.de> - 2023-03-14 21:00 +0100
                Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-15 08:30 +0100
                Re: OpenJDK package - JTREG 7.1 Emmanuel Bourg <ebourg@apache.org> - 2023-03-15 10:50 +0100
                Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-15 20:20 +0100
    Re: OpenJDK package - JTREG 7.1 Emmanuel Bourg <ebourg@apache.org> - 2023-03-15 16:30 +0100
      Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-15 23:10 +0100
        Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-15 23:20 +0100
          Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-28 22:40 +0200
            jtreg 7 vs. jtreg6 vs. testng vs. openjdk-8 (was Re: OpenJDK package  - JTREG 7.1) Thorsten Glaser <t.glaser@tarent.de> - 2023-03-29 21:30 +0200
        Re: OpenJDK package - JTREG 7.1 Thorsten Glaser <t.glaser@tarent.de> - 2023-03-15 23:20 +0100

csiph-web