| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
useful, but may also help identify Bazel as the culprit in the linked bug if we're lucky and the timestamps are clear.
--
PiperOrigin-RevId: 144359628
MOS_MIGRATED_REVID=144359628
|
|
|
|
|
|
|
|
| |
compilation actions.
--
PiperOrigin-RevId: 144356912
MOS_MIGRATED_REVID=144356912
|
|
|
|
|
|
|
|
| |
Moved some tests, fixed formatting, changed to use assertThat().
--
PiperOrigin-RevId: 144356402
MOS_MIGRATED_REVID=144356402
|
|
|
|
|
|
|
|
|
|
| |
behavior in the extended class owned by ResourceUsageAnalyzer. This makes the fix available to both Blaze and Bazel, since Bazel uses the AOSP released version of the com.tools.android.lint library, which contains ResourceUsageModel, instead of the source version available in [].
This change is based on the upstream patch [] and will be removed when the patch is included in the packaged version released with Bazel.
--
PiperOrigin-RevId: 144355049
MOS_MIGRATED_REVID=144355049
|
|
|
|
|
|
|
|
|
| |
(as they are for objc_library). This allows for swift/objc interop with
experimental_objc_library, since swift imports require compiled headers.
--
PiperOrigin-RevId: 144353367
MOS_MIGRATED_REVID=144353367
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144353268
MOS_MIGRATED_REVID=144353268
|
|
|
|
|
|
|
|
|
|
|
| |
Introduce helper classes whose d'tor automatically
release resources (close handles, release Java
object handles, etc) and get rid of the
"goto cleanup" pattern.
--
PiperOrigin-RevId: 144349886
MOS_MIGRATED_REVID=144349886
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144348933
MOS_MIGRATED_REVID=144348933
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
available to the extension registry generator.
With deploy_env, the message being extended may end up in the deploy_env binary's generated extension registry. However, the extension referencing that message is outside of deploy_env. For this case in the full runtime, we can synthesize the message as we don't need the loadPath (which is only used by lite runtime).
Rollback of commit 34de5d7d4a0678b3a4097cb7531fedb3ddb45983.
*** Reason for rollback ***
Rolling forward
*** Original change description ***
Automated [] rollback of commit fa7e34979b1a10794321b1233e8d6f44a62431fa.
--
PiperOrigin-RevId: 144346260
MOS_MIGRATED_REVID=144346260
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
See unknown commit
*** Original change description ***
Automated [] rollback of commit c9dbd4c1a4a4b4345c0b3924f86e01612ae12807.
*** Reason for rollback ***
Breaks bazel-docker-tests
http://ci.bazel.io/view/Dashboard/job/bazel-docker-tests/lastCompletedBuild/BAZEL_VERSION=HEAD,PLATFORM_NAME=docker/console
*** Original change description ***
Enable header compilation by default
--
PiperOrigin-RevId: 144344329
MOS_MIGRATED_REVID=144344329
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144342246
MOS_MIGRATED_REVID=144342246
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144339611
MOS_MIGRATED_REVID=144339611
|
|
|
|
|
|
|
|
| |
Fixes #1248.
--
PiperOrigin-RevId: 144333530
MOS_MIGRATED_REVID=144333530
|
|
|
|
|
|
|
|
| |
RELNOTES[INC]: All executable labels must also have a cfg parameter specified.
--
PiperOrigin-RevId: 144332992
MOS_MIGRATED_REVID=144332992
|
|
|
|
|
|
|
|
| |
Add Order#isCompatible, clean javadoc. Also fix broken @Deprecated-based canary for detecting accidental flattening.
--
PiperOrigin-RevId: 144331341
MOS_MIGRATED_REVID=144331341
|
|
|
|
|
|
|
|
| |
This fixes //src/test/java/com/google/devtools/build/lib:bazel-rules-tests.
--
PiperOrigin-RevId: 144328755
MOS_MIGRATED_REVID=144328755
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144325333
MOS_MIGRATED_REVID=144325333
|
|
|
|
|
|
|
|
|
|
| |
This was creating an invalid WORKSPACE file and then erroring out with a syntax error.
--
Change-Id: I59389f565a0a4a893659df8a0c29d4a5d7377e62
Reviewed-on: https://cr.bazel.build/8171
PiperOrigin-RevId: 144324721
MOS_MIGRATED_REVID=144324721
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144323833
MOS_MIGRATED_REVID=144323833
|
|
|
|
|
|
|
|
| |
See https://github.com/bazelbuild/bazel/issues/2107
--
PiperOrigin-RevId: 144321891
MOS_MIGRATED_REVID=144321891
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks //src/test/java/com/google/devtools/build/lib:bazel-rules-tests
http://ci.bazel.io/view/Dashboard/job/bazel-tests/BAZEL_VERSION=HEAD,PLATFORM_NAME=linux-x86_64/lastCompletedBuild/console
*** Original change description ***
aar_import provides JavaCompilationArgsProvider for DexArchiveAspect.
--
PiperOrigin-RevId: 144316524
MOS_MIGRATED_REVID=144316524
|
|
|
|
|
|
|
|
|
| |
See https://github.com/bazelbuild/bazel/issues/2107
See https://github.com/bazelbuild/bazel/issues/1744
--
PiperOrigin-RevId: 144313301
MOS_MIGRATED_REVID=144313301
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use CreateFileW to create the output files for
redirected stdout/stderr in nativeCreateProcess.
This way we can support long paths for these
files.
See https://github.com/bazelbuild/bazel/issues/2107
See https://github.com/bazelbuild/bazel/issues/2181
--
PiperOrigin-RevId: 144311729
MOS_MIGRATED_REVID=144311729
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a separate argument to nativeCreateProcess for
argv[0] specifically, and another for the rest of
the args.
In a subsequent change I'll add code to compute
the 8dot3 style short name of the argv[0] so we
can use longer paths for executables in
CreateProcessA than we normally could. This is the
same approach as used in commit 44ecf9a0c7c25496a43f59f1c8f20df9527e12cb
See https://github.com/bazelbuild/bazel/issues/2107
See https://github.com/bazelbuild/bazel/issues/2181
--
PiperOrigin-RevId: 144311562
MOS_MIGRATED_REVID=144311562
|
|
|
|
|
|
|
|
|
|
|
|
| |
in C++.
Protocol was already exposed for Python and Java, only make C++ a first class citizen.
--
Change-Id: Ib2aa45bdb534f0f9181483b0161f2aa7c857dfb4
Reviewed-on: https://cr.bazel.build/7814
PiperOrigin-RevId: 144300665
MOS_MIGRATED_REVID=144300665
|
|
|
|
|
|
|
|
| |
specify jar files containing Java resources.
--
PiperOrigin-RevId: 144299119
MOS_MIGRATED_REVID=144299119
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144296949
MOS_MIGRATED_REVID=144296949
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. no flag: only the direct reason is given (command execution termination status), and also the instruction to use "--verbose_failures"
2. flag "--verbose_failures": gives failed execution command and the instruction to use "--sandbox_debug --strategy"
3. flag "--verbose_failures --sandbox_debug": gives failed execution command, debugging message from sandboxing, and the instruction to use "--strategy"
Also removes "cd <sandbox_path>" in given failed command, since debugging is only necessary with flag "--verbose_failures --sandbox_debug" and the path is already given in sandboxing debugging message.
Addresses #2174.
Fixes bazel_sandboxing_test.sh and bazel_test_test.sh for the new error message.
Fixes timeout.
--
PiperOrigin-RevId: 144285435
MOS_MIGRATED_REVID=144285435
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
api_level is no longer required. It now sets the default android_sdk that is used if the --android_sdk flag is not passed. If it is not set, the highest api_level will be used as the default.
The new behavior is demonstrated by the following example:
$ ls $ANDROID_HOME/platforms
android-21 android-22 android-23
$ cat WORKSPACE
android_sdk_repository(
name = "foo",
)
$ bazel build //java/my/app # uses api level 23
$ bazel build --android_sdk=@foo//:sdk-22 //java/my/app # uses api level 22
$ cat > WORKSPACE <<EOF
android_sdk_repository(
name = "foo",
api_level = 21,
)
EOF
$ bazel build //java/my/app # uses api level 21
$ bazel build --android_sdk=@foo//:sdk-23 //java/my/app # uses api level 23
See https://github.com/bazelbuild/bazel/issues/2284 for the master plan for android_sdk_repository.
RELNOTES: android_sdk_repository no longer requires api_level. If one is not specified, the highest android platform installed will be used. Furthermore, android_sdk's are created for all android platforms installed and can be specified with the --android_sdk flag.
--
PiperOrigin-RevId: 144258881
MOS_MIGRATED_REVID=144258881
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144258810
MOS_MIGRATED_REVID=144258810
|
|
|
|
|
|
|
|
|
|
| |
incoming edges if dynamic configurations are turned on.
This CL does not cover top-level nodes.
--
PiperOrigin-RevId: 144258789
MOS_MIGRATED_REVID=144258789
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144257691
MOS_MIGRATED_REVID=144257691
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144256082
MOS_MIGRATED_REVID=144256082
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144231300
MOS_MIGRATED_REVID=144231300
|
|
|
|
|
|
|
|
|
|
| |
WindowsJniLoader.loadJniForTesting is just a
special case of what WindowsJniLoader.loadJni
already does, so we can just use the latter.
--
PiperOrigin-RevId: 144224388
MOS_MIGRATED_REVID=144224388
|
|
|
|
|
|
|
|
|
|
|
| |
New method to deserialize parsed resources.
Remove unthrown exceptions.
RELNOTES:None
--
PiperOrigin-RevId: 144221111
MOS_MIGRATED_REVID=144221111
|
|
|
|
|
|
|
|
| |
RELNOTES:None
--
PiperOrigin-RevId: 144218174
MOS_MIGRATED_REVID=144218174
|
|
|
|
|
|
|
|
| |
See https://github.com/bazelbuild/bazel/issues/2107
--
PiperOrigin-RevId: 144218095
MOS_MIGRATED_REVID=144218095
|
|
|
|
|
|
|
|
|
|
| |
--experimental_prune_more_modules. Both flags have proven to be stable for a
few weeks. Instead provide a (probably permanent) option to disable modules
pruning completely.
--
PiperOrigin-RevId: 144215146
MOS_MIGRATED_REVID=144215146
|
|
|
|
|
|
|
|
| |
* This new configuration allows for passthrough of Swift-specific options into Skylark for further consumption by swift_library. It also keeps things nicely isolated until we get a way to create configurations in Skylark directly.
--
PiperOrigin-RevId: 144210267
MOS_MIGRATED_REVID=144210267
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144207746
MOS_MIGRATED_REVID=144207746
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144207428
MOS_MIGRATED_REVID=144207428
|
|
|
|
|
|
|
|
|
| |
Bazel still supports java 7. This cl fixes a java 8-only construct introduced by commit 3c5e55ff8e058b624ce26e803ff00434c70d4b91.
Liam, feel free to fix it to your liking afterwards.
--
PiperOrigin-RevId: 144206418
MOS_MIGRATED_REVID=144206418
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Support passing /dev/null and NUL as flag values
for flags like --bazelrc.
In particular, special-case these paths in
methods like blaze_util::ReadFile,
blaze_util::IsDirectory, etc.
Fixes https://github.com/bazelbuild/bazel/issues/2354
RELNOTES[NEW]: Windows: "/dev/null" is now a supported path, e.g. --bazelrc=/dev/null now works
--
PiperOrigin-RevId: 144195994
MOS_MIGRATED_REVID=144195994
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144194956
MOS_MIGRATED_REVID=144194956
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144194918
MOS_MIGRATED_REVID=144194918
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If linkstatic was explicitly set to 0 for a non-test target, we didn't set
CcLibraryHelper to create CcLinkOutputs, but would still try to link those in
instead of the compile output. Instead, pull out a variable that puts this
logic into a single spot.
Also rename the flag to --experimental_link_compile_output_separately, which
IMO makes slightly more sense. Not too important as I don't think we should
keep this flag long-term anyway.
--
PiperOrigin-RevId: 144194903
MOS_MIGRATED_REVID=144194903
|
|
|
|
|
|
|
|
|
|
| |
agent through the $jacocorunner dependency.
They are either both linked in or neither of them is, so there isn't much point in separating them.
--
PiperOrigin-RevId: 144191570
MOS_MIGRATED_REVID=144191570
|
|
|
|
|
|
|
|
| |
Example of failure in Jenkins here: http://ci.bazel.io/job/bazel-tests/467/BAZEL_VERSION=HEAD,PLATFORM_NAME=linux-x86_64/console
--
PiperOrigin-RevId: 144185702
MOS_MIGRATED_REVID=144185702
|
|
|
|
|
|
|
|
|
|
| |
This is part of a series of changes to clean up the test strategies; this
specific change is a Google-internal refactoring. I'm planning to also update
the external test strategies subsequently.
--
PiperOrigin-RevId: 144184752
MOS_MIGRATED_REVID=144184752
|