| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
PiperOrigin-RevId: 192837552
|
|
|
|
|
| |
RELNOTES: n/a.
PiperOrigin-RevId: 192836316
|
|
|
|
|
|
|
|
|
| |
together) into two separate classpaths. This is the preparation cl. In the
following cls, I will graduately make the dependency issues clear, i.e., wether
it is a problem in the bootclasspath or the regular classpath.
RELNOTES: n/a.
PiperOrigin-RevId: 192828237
|
|
|
|
| |
PiperOrigin-RevId: 192802011
|
|
|
|
| |
PiperOrigin-RevId: 192539741
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 192452316
|
|
|
|
| |
PiperOrigin-RevId: 191970818
|
|
|
|
| |
PiperOrigin-RevId: 191961686
|
|
|
|
| |
PiperOrigin-RevId: 191948995
|
|
|
|
| |
PiperOrigin-RevId: 191809494
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The format of Truth's failure messages is about to change, which would break these tests.
Alternatively, I could modify these tests to accept both the old and new Truth message formats, but ideally most tests wouldn't rely on the exact message format at all.
(That suggests that an even better approach might be to just throw an exception whose message is a fixed string. That would avoid relying even on JUnit's message format, unlikely as I think that is to change.)
RELNOTES: None.
PiperOrigin-RevId: 190617095
|
|
|
|
|
|
|
|
|
|
|
| |
both the owner and the name. However, this is wrong, as the field reference or
method call may reference the same member with a different owner (e.g.,
subclass).
2) The type in ASM may refer to internal names, but also may refer to array descriptor. And arrays have methods such as clone(). Before, I just assume that a type can only be internal names.
RELNOTES: None.
PiperOrigin-RevId: 189630806
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rollforward as requested by the original author @hmemcpy.
*** Original change description ***
Skipping writing FILTERED tests to test.xml
This fixes #3201 by preventing tests that haven't actually run to be written to the test.xml. This is consistent with how e.g. surefire reports work, tests that were filtered out do not appear in the xml.
This allows changing the Bazel plugin in such a way that does not depend on `time` being 0.0.
Closes #4596.
PiperOrigin-RevId: 189610180
|
|
|
|
| |
PiperOrigin-RevId: 189380767
|
|
|
|
| |
PiperOrigin-RevId: 189225279
|
|
|
|
|
|
| |
Fixes bazelbuild/bazel#4846
PiperOrigin-RevId: 189123353
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently a test class annotated with `@Ignore` will cause the test
runner to fail with
```
Exception in thread "main" java.lang.IllegalArgumentException: Top test must be a suite
at com.google.testing.junit.runner.junit4.JUnit4TestModelBuilder.get(JUnit4TestModelBuilder.java:53)
```
This change treats classes with no tests (either no @Test annotations or
@Ignore at class level) as an empty test suite. The main motivation
behind this is allowing an entire test class to be ignored (e.g. to
quickly deal with a flaky test) without having to modify the BUILD file.
This is desirable in order to reduce the likelihood that a developer
forgets to update the BUILD file when removing the `@Ignore` annotation.
This pull request overrides the previous pull request
https://github.com/bazelbuild/bazel/pull/4073
Closes #4293.
PiperOrigin-RevId: 188850828
|
|
|
|
| |
PiperOrigin-RevId: 188799934
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rollback was requested by original authors @hmemcpy and @ittaiz in #3201:
"We found a problem with this patch... seems that tests that are added dynamically by the test runner (in our case, specs2 'examples' that are generated with Fragments.foreach) do not appear in the xml!"
This should be part of 0.12.0-rc1, otherwise that release will have the above mentioned regression.
*** Original change description ***
Skipping writing FILTERED tests to test.xml
This fixes #3201 by preventing tests that haven't actually run to be written to the test.xml. This is consistent with how e.g. surefire reports work, tests that were filtered out do not appear in the xml.
This allows changing the Bazel plugin in such a way that does not depend on `time` being 0.0.
Closes #4596.
PiperOrigin-RevId: 188455315
|
|
|
|
|
|
|
| |
warnings (--emit_errors or --noemit_errors).
RELNOTES:None.
PiperOrigin-RevId: 188397338
|
|
|
|
|
|
| |
RELNOTES:None.
PiperOrigin-RevId: 187711775
|
|
|
|
|
|
|
|
| |
The only two remaining users are for JAR, so directly call into BazelJavaBuilder rather than through our multiplex tool.
This requires opening the visibility of BazelJavaBuilder up to public.
PiperOrigin-RevId: 187690855
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 187571707
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The plugin tries to read the following attributes:
Target-Label: <label>
Injecting-Rule-Kind: <rule kind>
These are used instead of the jar owners passed to JavaBuilder from blaze. Any owners currently passed from blaze are now ignored.
This CL also half-reverts the command line syntax for JavaBuilder and Turbine. It is now:
--classpath <jar1> <jar2> ...
--direct_dependencies <jar1> ...
RELNOTES: None
PiperOrigin-RevId: 187419469
|
|
|
|
|
|
| |
now that Bazel no longer passes it.
PiperOrigin-RevId: 186708415
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Superceded by https://github.com/bazelbuild/bazel/commit/e734c479956df7a675c61f531d769609d3af3e5d
*** Original change description ***
JavaBuilder accepts a new --testonly argument to mark compilations of
test code. Error Prone will use these to distinguish between test and
production code, e.g. for enforcing @VisibleForTesting.
PiperOrigin-RevId: 186520809
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 186494122
|
|
|
|
|
| |
RELNOTES:n/a.
PiperOrigin-RevId: 186043433
|
|
|
|
| |
PiperOrigin-RevId: 185959149
|
|
|
|
|
|
|
|
|
| |
This fixes #3201 by preventing tests that haven't actually run to be written to the test.xml. This is consistent with how e.g. surefire reports work, tests that were filtered out do not appear in the xml.
This allows changing the Bazel plugin in such a way that does not depend on `time` being 0.0.
Closes #4596.
PiperOrigin-RevId: 185810400
|
|
|
|
|
|
| |
classpath heuristic
PiperOrigin-RevId: 185746460
|
|
|
|
|
|
| |
Roll forward of unknown commit
PiperOrigin-RevId: 185727344
|
|
|
|
|
|
|
|
|
|
|
| |
The values (if present) are written into the manifest with this format:
Target-Label: <label>
Injecting-Rule-Kind: <kind>
In the future, JavaBuilder will make sure of this instead of command line arguments to find owners for jars for its add_dep commands.
PiperOrigin-RevId: 185557317
|
|
|
|
|
|
| |
Fixes #4614
PiperOrigin-RevId: 185474153
|
|
|
|
|
|
|
|
| |
2) Also print the dependency issues to stderr.
3) Add golden tests to test the above two.
RELNOTES:n/a.
PiperOrigin-RevId: 185423338
|
|
|
|
| |
PiperOrigin-RevId: 185419668
|
|
|
|
|
| |
Change-Id: I1fa7867ffb08af95c1eef5ae3e32cff34292328b
PiperOrigin-RevId: 185189976
|
|
|
|
|
| |
RELNOTES:none.
PiperOrigin-RevId: 185075745
|
|
|
|
| |
PiperOrigin-RevId: 185003013
|
|
|
|
|
|
|
| |
series. The following CLs will integrate this into bazel.
RELNOTES:n/a.
PiperOrigin-RevId: 184706507
|
|
|
|
| |
PiperOrigin-RevId: 184370036
|
|
|
|
|
|
|
|
| |
To avoid hiding compiler.warn.sun.proprietary warnings when running with -Werror.
Fixes bazelbuild/bazel#4564
PiperOrigin-RevId: 184367653
|
|
|
|
|
|
| |
instead of directJarsToTargets/indirectJarsToTargets.
PiperOrigin-RevId: 183780563
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of passing:
--direct_dependency jar1 jarowner1 aspect1
--indirect_dependency jar2 jarowner2 aspect2
--classpath jar1 jar2
we pass
--dependencies jar1 jarowner1;aspect1 jar2 jarowner2:aspect2
--direct_dependencies jar1
This formats doesn't need to inspect each item in the incoming nested set, and thus doesn't need CustomMultiArgv.
This change needs to be rolled out in phases, so this CL changes JavaBuilder and Turbine to accept either format.
RELNOTES: None
PiperOrigin-RevId: 183155036
|
|
|
|
|
|
| |
Bazel bootstrap.
PiperOrigin-RevId: 183065122
|
|
|
|
|
|
| |
Fixes bazelbuild/bazel#4483
PiperOrigin-RevId: 182847474
|
|
|
|
| |
PiperOrigin-RevId: 182461095
|
|
|
|
| |
PiperOrigin-RevId: 182130131
|
|
|
|
|
|
|
|
| |
javac does not allow both -source and --release to be set, which makes it
difficult to migrate to --release when javacopts are combined from
multiple sources.
PiperOrigin-RevId: 182113897
|