Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B buck
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 201
    • Issues 201
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Meta
  • buck
  • Issues
  • #994
Closed
Open
Issue created Nov 03, 2016 by Administrator@rootContributor

Consider to integrate error prone out of the box in java build tool chain

Created by: davido

Gerrit Code Review can be compiled with most recent Buck version (d6949e14) without any issues.

With vanilla Bazel 0.4.0 Gerrit is failing to compile, though, and tells me that:

  $ bazel build gerrit
INFO: Found 1 target...
ERROR: /home/davido/projects/gerrit/gerrit-sshd/BUILD:5:1: Java
compilation in rule '//gerrit-sshd:sshd' failed: Worker process sent
response with exit code: 1.
bazel-out/local-fastbuild/bin/gerrit
-sshd/_javac/sshd/libsshd_sourcegenfiles/com/google/gerrit/sshd/AutoAnn
otation_Commands_named.java:52: error: [ConstantOverflow] Compile-time
constant expression overflows
        ((127 * 111972721) ^ (value.hashCode()));
                           ^
    (see http://errorprone.info/bugpattern/ConstantOverflow)
1 error
Target //:gerrit failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 2.393s, Critical Path: 2.17s

It turns out, this is a bug in auto-value dependency, that was fixed here: [1].

  • [1] https://github.com/google/auto/pull/371
Assignee
Assign to
Time tracking