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

Groups > linux.debian.maint.java > #9787 > unrolled thread

openjdk-9-jdk rebuild: Third pass

Back to article view | Back to linux.debian.maint.java

Contents

  openjdk-9-jdk rebuild: Third pass Chris West <solo-debian-java@goeswhere.com> - 2017-07-08 13:20 +0200
    RE: openjdk-9-jdk rebuild: Third pass "Ingo Bauersachs" <ingo@jitsi.org> - 2017-07-11 18:40 +0200
      Re: openjdk-9-jdk rebuild: Third pass Markus Koschany <apo@debian.org> - 2017-07-13 22:30 +0200

#9787 — openjdk-9-jdk rebuild: Third pass

Progress!

 * doko has uploaded openjdk-9 b177, which turns off some of the module
    checks, and fixes some other things
 * I've patched maven-javadoc-plugin (#866929), and doclint (#866908)
     locally, and both patches are probably okay
 * I've also hacked up javac to fixup -source and -target to 1.6, as
     we've still got issues with our hundreds of build systems.
     I'm not sure we can actually ship this patch[1], so we might
     additionally have a load of work fixing build systems to do.

Now, of 1925 packages, we have a 30% failure rate. That's much more like it!

Of the failures:

 16% are getting "cannot find symbol" errors:
  * many of these (e.g. maven2-core) hit this only during generating javadocs,
     has something happened to javadoc classpath generation in a build
     system, or is there something wrong with the javadoc command?
  * the rest are probably caused by module changes, e.g.
     javax.activation vanishing
  See the `symbol` folder in the build logs.

 15% are hitting encoding issues, despite the jh_build fix in #866845
   See the `encoding` folder in the build logs.

 <10% of packages (each) seem to be failing due to:
  * `cast` becoming illegal (this might be fixable with a lower -source)
  * `deps` not matching (packaging bug?)
  * `javadoc` failing, probably some overlap with the symbol errors above
  * `keyword` not available in this language version (lower -source in
      some cases)
  * obvious problems with `modules`
  * `tests` failing
  * `version` some error messages about versions, but probably not
     relevant as javac is fixing it

... leaving just 125 packages with `unknown` problems,  e.g.
  * build script tries to check jdk version and fails horribly (glugen)
  * assuming presence of tools.jar (aspectj-maven-plugin)
  * bugs in the builder
  * failures in the builder that probably wouldn't happen on the buildd
  * packages that are broken anyway (diffoscope)
  * eclipse
  * name clashes (maven-war-plugin)

Doesn't look like anything more to fix in the toolchain, so, er...

Time for a mass bug filing (~300)? Perhaps less useful as the majority
of the packages are maintained by people reading this mail.


Build logs: https://rbuild.fau.xxx/2017-07-07/

My personal favourites from this round:
 * The doclint change is in a file named WorkArounds.java[2], which is a
    copy-paste of another file, added in a commit named "Merge", very
    shortly before the "implement modules" megacommit.
 * libbluray is broken due to the addition of an abstract method (i.e.
    no default) to the java.io.FileSystem[3] interface, which I never liked.

Chris.

1: https://github.com/FauxFaux/debjdk9/blob/master/jdk/allow-old-source-versions.diff
2: https://github.com/FauxFaux/jdk9-flat/blob/f3edcfbd7946e21be277edf33e7b1d8000516c36/langtools/src/jdk.javadoc/share/classes/jdk/javadoc/internal/doclets/toolkit/WorkArounds.java#L114
3: https://github.com/FauxFaux/jdk9-flat/blame/f3edcfbd7946e21be277edf33e7b1d8000516c36/jdk/src/java.base/share/classes/java/io/FileSystem.java#L215

[toc] | [next] | [standalone]

#9791

> From: Chris West [mailto:solo-debian-java@goeswhere.com]
> 
> [...]
> 
>  16% are getting "cannot find symbol" errors:
>   * many of these (e.g. maven2-core) hit this only during generating
> javadocs,
>      has something happened to javadoc classpath generation in a build
>      system, or is there something wrong with the javadoc command? * the
>      rest are probably caused by module changes, e.g. javax.activation
>      vanishing
>   See the `symbol` folder in the build logs.

I'm not sure if this is the right place to discuss individual packages.
However, I noticed that dnsjava is among the packages failing with missing
symbols. dnsjava in Debian is using the Maven pom maintained at [1]. I've
added some profiles there to make it compile with JDK 9.

Regards,
Ingo

[1] https://github.com/dnsjava/dnsjava

[toc] | [prev] | [next] | [standalone]

#9796

[Multipart message — attachments visible in raw view] — view raw

Am 11.07.2017 um 18:38 schrieb Ingo Bauersachs:

> I'm not sure if this is the right place to discuss individual packages.
> However, I noticed that dnsjava is among the packages failing with missing
> symbols. dnsjava in Debian is using the Maven pom maintained at [1]. I've
> added some profiles there to make it compile with JDK 9.

I recommend to file bug reports against affected packages because they
won't get lost and are always visible. It is probably to early for a
mass bug filing but if you already know solutions for specific Java 9
issues, don't hesitate to report them, e.g. with reportbug [1] or
directly via your favorite e-mail client (apparently Outlook, urgh).

Regards,

Markus

[1] https://wiki.debian.org/reportbug

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.java

csiph-web