Mailing List Archive

RE: [JENKINS-EA] Lucene-main-Linux (64bit/jdk-16-ea+36) - Build # 29666 - Failure!
Hi,

it looks like due to the split something went wrong, because with JDK 16 the build fails - no change, but suddenly fails:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':checkUnusedConstraints'.
> There are unused pins in your versions.props:
[com.google.guava:guava, com.google.errorprone:*, com.google.protobuf:protobuf-java, com.github.ben-manes.caffeine:caffeine]

Rerun with --fix to remove them.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.6.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 16m 2s

I see no commit that may cause this, so I have the feeling it's java 16 only. Dawid, do you have an idea?

-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: uwe@thetaphi.de

> -----Original Message-----
> From: Policeman Jenkins Server <jenkins@thetaphi.de>
> Sent: Thursday, March 11, 2021 8:37 PM
> To: builds@lucene.apache.org
> Subject: [JENKINS-EA] Lucene-main-Linux (64bit/jdk-16-ea+36) - Build # 29666 -
> Failure!
> Importance: Low
>
> Build: https://jenkins.thetaphi.de/job/Lucene-main-Linux/29666/
> Java: 64bit/jdk-16-ea+36 -XX:+UseCompressedOops -XX:+UseG1GC
>
> All tests passed


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
RE: [JENKINS-EA] Lucene-main-Linux (64bit/jdk-16-ea+36) - Build # 29666 - Failure! [ In reply to ]
I think I know why this happens:

Before the split of solr and lucene, the solr part used some annotations of errorprone in its build. Because of that, errorprone dependencies were always used (downloaded), so palantir was happy.

Lucene does not use any errorprone JARs in its compile classpath. When then JDK 16 disables errorprone (see the if statement), Palantir sees no usage of the dependency anymore.

I think we must either put that on some white- ääääähm exclusion-list!

Dawid, does this sound correct?

-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: uwe@thetaphi.de

> -----Original Message-----
> From: Uwe Schindler <uwe@thetaphi.de>
> Sent: Thursday, March 11, 2021 9:34 PM
> To: dev@lucene.apache.org
> Cc: Dawid Weiss <dweiss@apache.org>
> Subject: RE: [JENKINS-EA] Lucene-main-Linux (64bit/jdk-16-ea+36) - Build #
> 29666 - Failure!
>
> Hi,
>
> it looks like due to the split something went wrong, because with JDK 16 the
> build fails - no change, but suddenly fails:
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':checkUnusedConstraints'.
> > There are unused pins in your versions.props:
> [com.google.guava:guava, com.google.errorprone:*,
> com.google.protobuf:protobuf-java, com.github.ben-manes.caffeine:caffeine]
>
> Rerun with --fix to remove them.
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or --debug
> option to get more log output. Run with --scan to get full insights.
>
> * Get more help at https://help.gradle.org
>
> Deprecated Gradle features were used in this build, making it incompatible
> with Gradle 7.0.
> Use '--warning-mode all' to show the individual deprecation warnings.
> See
> https://docs.gradle.org/6.6.1/userguide/command_line_interface.html#sec:co
> mmand_line_warnings
>
> BUILD FAILED in 16m 2s
>
> I see no commit that may cause this, so I have the feeling it's java 16 only.
> Dawid, do you have an idea?
>
> -----
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
> > -----Original Message-----
> > From: Policeman Jenkins Server <jenkins@thetaphi.de>
> > Sent: Thursday, March 11, 2021 8:37 PM
> > To: builds@lucene.apache.org
> > Subject: [JENKINS-EA] Lucene-main-Linux (64bit/jdk-16-ea+36) - Build #
> 29666 -
> > Failure!
> > Importance: Low
> >
> > Build: https://jenkins.thetaphi.de/job/Lucene-main-Linux/29666/
> > Java: 64bit/jdk-16-ea+36 -XX:+UseCompressedOops -XX:+UseG1GC
> >
> > All tests passed
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS-EA] Lucene-main-Linux (64bit/jdk-16-ea+36) - Build # 29666 - Failure! [ In reply to ]
> I think we must either put that on some white- ääääähm exclusion-list!

I'll fix it.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS-EA] Lucene-main-Linux (64bit/jdk-16-ea+36) - Build # 29666 - Failure! [ In reply to ]
I changed the code to always include errorprone dependency -
regardless of whether we
actually run the check or not. This is the simplest way to achieve
consistency here. Thanks for tracking this down, Uwe.


Dawid

On Thu, Mar 11, 2021 at 10:21 PM Dawid Weiss <dweiss@apache.org> wrote:
>
> > I think we must either put that on some white- ääääähm exclusion-list!
>
> I'll fix it.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org