| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 178448614
|
|
|
|
| |
PiperOrigin-RevId: 178176824
|
|
|
|
|
|
| |
Follow-up to https://github.com/bazelbuild/bazel/commit/0b2352de3101e87647d083f6089246079dda0f75
PiperOrigin-RevId: 177415788
|
|
|
|
|
|
| |
See bazelbuild/bazel#4165.
PiperOrigin-RevId: 177254510
|
|
|
|
|
|
| |
Follow-up to https://github.com/bazelbuild/bazel/commit/0b2352de3101e87647d083f6089246079dda0f75
PiperOrigin-RevId: 177234776
|
|
|
|
| |
PiperOrigin-RevId: 177138150
|
|
|
|
|
|
| |
Blaze now passes class paths as individual arguments, instead of a pre-joined.
PiperOrigin-RevId: 177112933
|
|
|
|
|
|
| |
This avoids bazelbuild/bazel#4108.
PiperOrigin-RevId: 177096864
|
|
|
|
|
|
|
|
|
|
|
| |
to rules that use the $(JAVA) or the $(JAVABASE) Make variable.
This is necessary because a future Blaze version will require this for rules that use said Make variables. This incompatible change can be tested today by adding the --noexperimental_enable_jvm_configuration_make_variables command line option to Blaze.
This change is part of a large-scale change ([]
RELNOTES: None.
PiperOrigin-RevId: 176834987
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use try-with-resources to close all streams.
I hope this will fix the spurious file deletion
failures on Windows, where the persistent
JavaBuilder worker cannot delete outputs from
previous builds because, supposedly, they are
still open, because a stale object that's ready
to be GC'd hasn't yet been actually GC'd.
Change-Id: Ia57b8bd0ba1b6ee0691d34467c92e86e35d4d71d
PiperOrigin-RevId: 175941520
|
|
|
|
| |
PiperOrigin-RevId: 175709097
|
|
|
|
| |
PiperOrigin-RevId: 174354036
|
|
|
|
|
|
|
|
|
| |
This happens when a sh_test has a dependency on a java_binary, so
JACOCO_METADATA_JAR is not set and coverage should not be run on the
java_binary.
RELNOTES: None.
PiperOrigin-RevId: 172881410
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 172545302
|
|
|
|
| |
PiperOrigin-RevId: 172365313
|
|
|
|
| |
PiperOrigin-RevId: 171245323
|
|
|
|
| |
PiperOrigin-RevId: 171209823
|
|
|
|
| |
PiperOrigin-RevId: 170960535
|
|
|
|
| |
PiperOrigin-RevId: 170752570
|
|
|
|
|
|
|
|
|
| |
as it was not part of a valid junit xml schema.
To cherry-pick for #3286.
RELNOTES: None.
PiperOrigin-RevId: 170022796
|
|
|
|
| |
PiperOrigin-RevId: 170022704
|
|
|
|
|
|
|
|
|
|
|
| |
When a timeout occurred, the current test case is interrupted and the others are cancelled. This was not reflected in any way and all tests were reported as success, even if there was a timeout and the tests were cancelled/interrupted.
Also add a status xml attribute to mark if the test was completed, cancelled or interrupted.
Fixes #3763
RELNOTES: None.
PiperOrigin-RevId: 169665622
|
|
|
|
|
|
|
|
|
| |
Those files are not linked anywhere and where removed by the
export process either by accident or for better support from IntelliJ.
According to ij.bazel.build a non linked target will not be analyzed
so it should be safe.
PiperOrigin-RevId: 169229654
|
|
|
|
|
|
|
|
|
| |
This and further changes may contain minor modifications to BUILD files that
don't serve any apparent purpose. The reason for these changes is that we're
switching from checked-in BUILD files to generated BUILD files, and there may
be small differences between these files.
PiperOrigin-RevId: 168201282
|
|
|
|
|
|
|
|
|
| |
fixes #3285
kept the existing message in case someone is parsing this text
Closes #3677.
PiperOrigin-RevId: 167707934
|
|
|
|
|
|
|
|
|
| |
Split collect, concurrent, vfs, windows into package-level BUILD files.
Move clock classes out of "util", into their own Java package.
Move CompactHashSet into its own Java package to break a dependency cycle.
Give nestedset and inmemoryfs their own package-level BUILD files.
PiperOrigin-RevId: 167702127
|
|
|
|
| |
PiperOrigin-RevId: 167520688
|
|
|
|
|
| |
Change-Id: I3fce66ec2e63d152aafc0cf9ea067d6dbf1245f7
PiperOrigin-RevId: 167484075
|
|
|
|
| |
PiperOrigin-RevId: 166849610
|
|
|
|
|
|
|
|
| |
indirectly depend on it by using the $(JAVABASE) or $(JAVA) Make variables.
It was tested by running "bazel build --nobuild" on the affected targest to make sure that they still work.
PiperOrigin-RevId: 166695324
|
|
|
|
|
|
|
|
|
| |
This and further changes may contain minor modifications to BUILD files that
don't serve any apparent purpose. The reason for these changes is that we're
switching from checked-in BUILD files to generated BUILD files, and there may
be small differences between these files.
PiperOrigin-RevId: 166684362
|
|
|
|
| |
PiperOrigin-RevId: 165439218
|
|
|
|
|
|
|
| |
new blaze Java implementation sends the runtime jars encapsulated in a metadata
txt file, instead of listing them in the environment variable. The previous approach led to blaze crashing with an "Argument list too long" error.
PiperOrigin-RevId: 165155269
|
|
|
|
| |
PiperOrigin-RevId: 165003777
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use $(location) to get the unittest.bash script, which allows this test to also
run with a different label prefix. This involves removing the intermediate
testenv.sh script, which doesn't seem to add much value.
We might want to consider a sh_unit_test rule or macro that has an implicit
dependency on the unittest.bash script and doesn't require every test to do
this manually.
PiperOrigin-RevId: 164846477
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 164667144
|
|
|
|
| |
PiperOrigin-RevId: 164446300
|
|
|
|
| |
PiperOrigin-RevId: 164252615
|
|
|
|
| |
PiperOrigin-RevId: 163840258
|
|
|
|
|
|
|
|
|
|
| |
Adds back a compiler test empty .cc file. Seems to be an omission in https://github.com/bazelbuild/bazel/commit/65cda4f219e564ccb190b2992151658dfae9904
The _is_gold_supported check in unix_cc_configure.bzl always fails without this change, since the file it's checking with isn't created. Looks like there may be other effects through _add_option_if_supported, although I only noticed because apparently I have written linker-specific code.
Closes #3484.
PiperOrigin-RevId: 163832465
|
|
|
|
|
|
|
|
|
| |
This and further changes may contain minor modifications to BUILD files that
don't serve any apparent purpose. The reason for these changes is that we're
switching from checked-in BUILD files to generated BUILD files, and there may
be small differences between these files.
PiperOrigin-RevId: 163525889
|
|
|
|
|
|
|
|
|
|
| |
After running the new coverage implementation on some real targets I found the following.
1. Inner classes with the same name could be added from different jars. Addressed this by analyzing classes with the same name exactly once.
2. Auto-generated files were added to the coverage report. This is resolved first on the blaze/bazel side by adding to the files with the exec paths of the instrumented files only those that are source files and on the coverage runner side by discarding all the files that are not in that file.
PiperOrigin-RevId: 162478894
|
|
|
|
| |
PiperOrigin-RevId: 162263240
|
|
|
|
|
|
|
|
|
|
| |
The new implementation doesn't use one metadata jar for the whole build anymore, but wraps all the uninstrumented classes in each of the build jars, among with a txt file that contains the paths of the files to be instrumented. The paths will be used to output the entire relative filepath to the partial coverage report.
Instead of one metadata jar containing all uninstrumented classes on the runtime classpath, the coverage runner will retrieve all the build jars on the runtime classpath.
Because the build jars contain now both classes and uninstrumented classes, the coverage runner will not analyze the entire given jar, but only the classes in the given jars that have the right suffix.
PiperOrigin-RevId: 161951370
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes a minor regression introduced by bazelbuild/bazel@2c3c87fab48646167e4233f539540df6b5ed3d04.
mktemp's interface changed in OS X 10.11 to allow the prefix to be
unspecified, but not specifying the prefix will cause the command to
error out on OS X 10.10 and earlier.
Closes #3281.
PiperOrigin-RevId: 161805877
|
|
|
|
|
|
|
|
| |
And instead rely on the flags being set in java_toolchain.jvm_opts.
This change is being made in preparation for JDK 9, which replaces
-Xbootclasspath/p with --patch-module.
PiperOrigin-RevId: 161620182
|
|
|
|
|
|
| |
The new implementation doesn't use the metadata jar anymore, but wraps all the uninstrumented classes in the build jar among with a txt file that contains the paths of the files to be instrumented.
PiperOrigin-RevId: 161499019
|
|
|
|
|
|
|
|
|
|
| |
it has been replaced by -XepDisableAllChecks, which disables all Error Prone
checks instead of disabling the plugin. Disabling the plugin entirely breaks
handling of other -Xep flags.
RELNOTES[INC]: -extra_checks:off is no longer supported; use -XepDisableAllChecks instead
PiperOrigin-RevId: 161127522
|
|
|
|
| |
PiperOrigin-RevId: 161127284
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
See bazelbuild/bazel#3172
*** Original change description ***
Add an experimental flag to Turbine to indicate to annotation processors that they are running in hjar compilation
PiperOrigin-RevId: 159585343
|