| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
doesn't conflict with whatever AutoValue version the code under test has.
Fixes #2044.
--
MOS_MIGRATED_REVID=138618191
|
|
|
|
|
|
|
|
| |
-Xlintdoc:reference causes javac to load symbols referenced in javadoc, which
may fail with the reduced classpath optimization enabled.
--
MOS_MIGRATED_REVID=138529301
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138223170
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137669164
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137500893
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137495530
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137464177
|
|
|
|
|
|
|
|
|
|
| |
to java/c/g/testing/junit/runner/sharding/testing. Also:
- Remove Guava dependencies and fix minor style issues in FakeShardingFilters
- Fix lint issues in TestSuite[]ModelTest
--
MOS_MIGRATED_REVID=136840327
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll-forward with fix.
Tested with `bazel build src:srcs //src/test/...` using a bootstrapped bazel.
Fixes #1923.
RELNOTES[INC]: Non test-only targets can no longer depends on test-only targets.
*** Original change description ***
Automated [] rollback of commit a9f20b0d6459d395444c45cf5e94a899f3443633.
*** Reason for rollback ***
Broke Bazel CI:
ERROR: /home/ci/workspace/Bazel/JAVA_VERSION/1.8/PLATFORM_NAME/linux-x86_64/src/BUILD:284:1: in filegroup rule //src:srcs: non-test target '//src:srcs' depends on testonly target '//src/java_tools/junitrunner/java/com/google/testing/junit/junit4:srcs' and doesn't have testonly attribute set.
ERROR: Analysis of target '//scripts/packages:packages' failed; build aborted.
http://ci.bazel.io/view/Bazel%20b...
***
--
MOS_MIGRATED_REVID=136589937
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=135942005
|
|
|
|
|
|
|
| |
package.
--
MOS_MIGRATED_REVID=135869348
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=135810752
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
This CL is causing failures in one of our integration tests:
//javatests/com/google/security/authorization/sphinx/integration:SimpleUIEditorPageE2eTest_firefox-linux
[] link:
[]
Note: Specifically, it looks like BinStackingShardingFilterFactory.java pointing to the branched RuntimeCost annotation is causing the failures.
I tried to change our test to point to the branched RuntimeCost annotation but Target '//third_party/bazel/src/java_tools/junitrunner/java/com/google/testing/junit/runner/sharding/weighted:weighted' is not visible.
*** Original change description ***
Branched internal RuntimeCost in junitrunner.
RuntimeCost class is needed by the package com.google.testing.junit.runner.sharding.weighted. I branched it from the internal code because the weighted package is now open sourced and does not have access to the previous import.
This didn't break Bazel before because there was no dependency to the weighted target when building BazelTestRunner. I catched this trying to open-source junitrunner tests.
--
MOS_MIGRATED_REVID=135734237
|
|
|
|
|
|
|
|
|
|
|
|
| |
c.g.testing.junit.runner.internal.junit4
Other minor changes:
- reduce visibility of MemoizingRequest.createRunner()
- Fix bug in CancellableRequestFactory where createRequest() can be called multiple times
--
MOS_MIGRATED_REVID=135722005
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=135388964
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=135171940
|
|
|
|
|
|
|
|
| |
c.g.testing.junit.junit4.runner.internal or
c.g.testing.junit.junit4.runner.internal.junit4
--
MOS_MIGRATED_REVID=135003685
|
|
|
|
|
|
|
| |
java_proto_library), pass it the kind of the rule.
--
MOS_MIGRATED_REVID=134694958
|
|
|
|
|
|
|
| |
c.g.testing.junit.junit4.runner.
--
MOS_MIGRATED_REVID=134685188
|
|
|
|
|
|
|
|
|
| |
RuntimeCost class is needed by the package com.google.testing.junit.runner.sharding.weighted. I branched it from the internal code because the weighted package is now open sourced and does not have access to the previous import.
This didn't break Bazel before because there was no dependency to the weighted target when building BazelTestRunner. I catched this trying to open-source junitrunner tests.
--
MOS_MIGRATED_REVID=134634122
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134546010
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134486526
|
|
|
|
|
|
|
| |
junitrunner/java/com/google/testing/junit/runner/sharding/weighted.
--
MOS_MIGRATED_REVID=134046554
|
|
|
|
|
|
|
| |
inject custom extra data (link, icons, etc) so that a test method can be associated with an external tool.
--
MOS_MIGRATED_REVID=133912980
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133899664
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133894022
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, all classes from the symbol table are added to jdeps,
even if some of them haven't been resolved and as such aren't
actually used. This causes siblings from other jars (such as
R.java) to be added to jdeps, even though they are not actually
referenced. Mark these with Kind.UNRESOLVED to allow code to
discard these.
All non-test code that references Kind.IMPLICIT has been
modified to also check for Kind.INCOMPLETE to keep
the current behavior unchanged.
Eg:
jar liba.jar:
package a;
class A {
void test() {
// Use R.id
}
}
jar liba_resources.jar:
package a;
class R {
}
package b;
import a;
class MyClass {
A a = new A();
}
---> jdeps will contain both liba.jar, liba_resources.jar
the latter will now have Kind.INCOMPLETE.
--
MOS_MIGRATED_REVID=133791687
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133756960
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks TensorFlow and other Bazel jobs on ci.bazel.io
*** Original change description ***
Change execution root for external repositories to be ../repo
Some of the important aspect of this change:
* Remote repos in the execution root are under output_base/execroot/repo_name, so the prefix is ../repo_name (to escape the local workspace name).
* Package roots for external repos were previously "output_base/", they are now output_base/external/repo_name (which means source artifacts always have a relative path from their repository).
* Outputs are under bazel-bin/external/repo_name/ (or similarly under genfiles). Note that this is a bit of a change from how this was implemented in the previous cl.
Fixes #1262.
RELNOTES[INC]: Previously, an external repository would be symlinked into the
execution root at execroot/local_repo/external/remote_repo. This changes it to
be at execroot/remote_repo. This may break genrules/Skylark actions that
hardcode execution root paths. If this causes breakages for you, ensure that
genrules are using $(location :target) to access files and Skylark rules are
using http://bazel.io/docs/skylark/lib/File.html's path, dirname, etc.
functions.
Roll forward of bdfd58a.
--
MOS_MIGRATED_REVID=133709658
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some of the important aspect of this change:
* Remote repos in the execution root are under output_base/execroot/repo_name, so the prefix is ../repo_name (to escape the local workspace name).
* Package roots for external repos were previously "output_base/", they are now output_base/external/repo_name (which means source artifacts always have a relative path from their repository).
* Outputs are under bazel-bin/external/repo_name/ (or similarly under genfiles). Note that this is a bit of a change from how this was implemented in the previous cl.
Fixes #1262.
RELNOTES[INC]: Previously, an external repository would be symlinked into the
execution root at execroot/local_repo/external/remote_repo. This changes it to
be at execroot/remote_repo. This may break genrules/Skylark actions that
hardcode execution root paths. If this causes breakages for you, ensure that
genrules are using $(location :target) to access files and Skylark rules are
using http://bazel.io/docs/skylark/lib/File.html's path, dirname, etc.
functions.
Roll forward of bdfd58a.
--
MOS_MIGRATED_REVID=133606309
|
|
|
|
|
|
|
|
|
| |
javac fakes up a type int the AST for implicitly typed lambda parameters, and
uses JCLambda#paramKind to distinguish between implicit and explicit types. We
only want to record explicit lambda parameter types as direct uses in SJD.
--
MOS_MIGRATED_REVID=133446081
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133255417
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132965726
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is part of an initiative to remove Dagger from junitrunner. Because
there are too many interdependent components that Dagger touches, its usage
cannot be easily removed in small independent changes. Therefore the first step
is to check in the code that Dagger generates (with slighty small changes, e.g.
classes were renamed, some Dagger specific data types were changed to junitrunner internal types).
The following steps include removing all the Dagger annotations and BUILD
dependencies, and refactoring the generated code.
--
MOS_MIGRATED_REVID=132543906
|
|
|
|
|
|
|
|
|
|
| |
All usage of Guava has been removed from junitrunner. It is now safe to also remove
all deps from the BUILD files.
Fixing issue #1150.
--
MOS_MIGRATED_REVID=132252042
|
|
|
|
|
|
|
|
|
|
|
| |
Bazel users that are using a different Guava version than the one in the
junitrunner jar are getting an IncompatibleClassChangeError. Rewriting
parts of junitrunner code so it won't depend on Guava anymore.
Continuing progress on issue #1150.
--
MOS_MIGRATED_REVID=132054901
|
|
|
|
|
|
|
|
|
|
|
| |
Bazel users that are using a different Guava version than the one in the
junitrunner jar are getting an IncompatibleClassChangeError. Rewriting
parts of junitrunner code so it won't depend on Guava anymore.
Continuing progress on issue #1150.
--
MOS_MIGRATED_REVID=131938872
|
|
|
|
|
|
|
|
|
|
|
| |
Bazel users that are using a different Guava version than the one in the
junitrunner jar are getting an IncompatibleClassChangeError. Rewriting
parts of junitrunner code so it won't depend on Guava anymore.
Continuing progress on issue #1150.
--
MOS_MIGRATED_REVID=131807036
|
|
|
|
|
|
|
|
|
|
|
| |
Bazel users that are using a different Guava version than the one in the
junitrunner jar are getting an IncompatibleClassChangeError. Rewriting
parts of junitrunner code so it won't depend on Guava anymore.
Continuing progress on issue #1150.
--
MOS_MIGRATED_REVID=131806984
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=131734056
|
|
|
|
|
|
|
| |
Fixes #1614.
--
MOS_MIGRATED_REVID=131701262
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Original change by elenairina@elenairina:incompatible-guava5:667:citc on 2016/08/24 08:03:39.
Original change ignored the fact that LinkedListMultimap and ConcurrentHashMap
handle the get operation differently. The first one returns an empty collection when
there is nothing associated with a given key in the data structure, while the
latter simply returns null.
Removing some of GUAVA dependencies from junit.runner.junit4 and -.model
Bazel users that are using a different Guava version than the one in the
junitrunner jar are getting an IncompatibleClassChangeError. Rewriting
parts of junitrunner code so it won't depend on Guava anymore.
Continuing progress on issue #1150.
--
MOS_MIGRATED_REVID=131695499
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=131181548
|
|
|
|
|
|
|
|
|
|
|
| |
Bazel users that are using a different Guava version than the one in the
junitrunner jar are getting an IncompatibleClassChangeError. Rewriting
parts of junitrunner code so it won't depend on Guava anymore.
Continuing progress on issue #1150.
--
MOS_MIGRATED_REVID=131172156
|
|
|
|
|
|
|
|
| |
RELNOTES:
Add worker support to []SingleJar.
--
MOS_MIGRATED_REVID=131133478
|
|
|
|
|
|
|
| |
--
Change-Id: I89804f0993e0248e23ee61c527117a9592a828da
Reviewed-on: https://bazel-review.googlesource.com/#/c/5550/3
MOS_MIGRATED_REVID=131092172
|
|
|
|
|
|
|
|
| |
RELNOTES:
Add worker support to single jar.
--
MOS_MIGRATED_REVID=131043398
|
|
|
|
|
|
|
|
|
|
|
| |
Bazel users that are using a different Guava version than the one in the
junitrunner jar are getting an IncompatibleClassChangeError. Rewriting
parts of junitrunner code so it won't depend on Guava anymore.
Continuing progress on issue #1150.
--
MOS_MIGRATED_REVID=130946174
|
|
|
|
|
|
|
|
|
| |
This change is necessary due to recent move away from Guava immutable collections (which returns null in case of non-existing item) to Java native ones (some of which throws exceptions).
One such use case where it was breaking the code was tests that uses junitparam, which might be an indication of another problem.
--
MOS_MIGRATED_REVID=130321230
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
& util).
Bazel users that are using a different Guava version than the one in the
junitrunner jar are getting an IncompatibleClassChangeError. Rewriting
parts of junitrunner code so it won't depend on Guava anymore.
Continuing progress on issue #1150.
Removing most of Guava dependencies from junit.runner.sharding. A more
significant change regards rewriting Guava method
assertThat().containsExactlyElementsIn().
Also removing previous trailing spaces.
--
MOS_MIGRATED_REVID=129992951
|