| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
HIDDEN.
PiperOrigin-RevId: 158524495
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was originally included in runtime due to external dependencies, and
a desire to keep the options parser a general options library. These
dependencies have been or will be removed, and there are plenty of other
general flag libraries.
InvocationPolicy is fundamentally acting on the properties of this
specific OptionsParser and needs proper access to it for the proper
solution to a number of existing bugs, which means having access to
things that should be package private.
PiperOrigin-RevId: 158523111
|
|
|
|
|
|
| |
This fixes an exception being thrown and logged by the remote worker process
(//src/tools/remote_worker:remote_worker) every time the remote worker attempts
to access the remote REST cache.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows writing integration tests in Python
rather than shell, so we can avoid
https://github.com/bazelbuild/bazel/issues/3148
This change also adds a test to verify that
running "bazel info server_pid" twice yields the
same PID. Again, this is testing that we indeed
avoid the aformentioned bug.
Change-Id: Ic800965b16ab87179370fd2cd43908286120e8d5
PiperOrigin-RevId: 158517192
|
|
|
|
|
| |
Change-Id: I8e445d3f3b06846a2f1d8db25c98aa5cd124f72b
PiperOrigin-RevId: 158516752
|
|
|
|
|
|
|
| |
Fixes #2904.
RELNOTES: None.
PiperOrigin-RevId: 158516169
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also use DigestUtils for performance, which has a static cache of the digests.
This isn't ideal, but necessary for now to avoid computing the digests multiple
times. We'll need to clean this up afterwards by including the digests in the
posted events, and making them available to the PathConverter. I have some
changes towards that (as well as some submitted already), but it requires
quite some refactoring.
RELNOTES: Bazel posts links to the CAS to the BEP if remote caching / execution is enabled
PiperOrigin-RevId: 158513165
|
|
|
|
|
|
|
|
|
| |
This integration test is about the UI, so any tests the
bazel under test executes are toy examples. So there is
no reason not to run them locally.
RELNOTES: None
PiperOrigin-RevId: 158509077
|
|
|
|
|
|
| |
We don't want people to get used to this.
PiperOrigin-RevId: 158508816
|
|
|
|
| |
PiperOrigin-RevId: 158503746
|
|
|
|
|
|
|
|
|
| |
--experimental_extra_action_top_level_only_with_aspects command line option.
It was introduced in November 2016 as an escape hatch, and has not been used in the last two months so it's safe to remove.
RELNOTES: None.
PiperOrigin-RevId: 158502426
|
|
|
|
|
|
|
|
| |
The base names are not necessarily unique enough to identify which
artifact is being talked about.
Change-Id: Ic8ff78c8f26f98e0e9a2d558d03f4cf9ae9111c8
PiperOrigin-RevId: 158499210
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 158498863
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 158497633
|
|
|
|
|
|
|
|
|
| |
https://docs.google.com/document/d/1AaGk7fOPByEvpAbqeXIyE8HX_A3_axxNnvroblTZ_6s/edit
Also refactored away the various *Interface* files, no need since unit testing can be done with mocking the appropriate gRPC Impl classes directly (see tests). This also fixes the RemoteSpawnRunner, which should use different objects for remote caching and remote execution, the same way RemoteSpawnStrategy does.
RELNOTES: n/a
PiperOrigin-RevId: 158473700
|
|
|
|
| |
PiperOrigin-RevId: 158473075
|
|
|
|
|
|
|
| |
This change moves the BES code from blaze to bazel.
RELNOTES: None.
PiperOrigin-RevId: 158445754
|
|
|
|
|
| |
Change-Id: I9652195e3f8d6f7912a1c52880f23114d34c6ebf
PiperOrigin-RevId: 158439371
|
|
|
|
| |
PiperOrigin-RevId: 158433594
|
|
|
|
| |
PiperOrigin-RevId: 158430272
|
|
|
|
| |
PiperOrigin-RevId: 158428641
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(Automated g4 rollback of commit 23004957a56d304106d5dbf0d6ea52ec10713b39).
*** Reason for rollback ***
The problems that forced commit 23004957a56d304106d5dbf0d6ea52ec10713b39 were fixed in commit e6392cd380fce14d719890c78d5eb2657e8a6cfc.
*** Original change description ***
Automated g4 rollback of commit e7ab452ac940e645046221dee9b63a670f8a276c.
*** Reason for rollback ***
Some of the work supporting this is being rolled back due to uncaught crash bugs.
*** Original change description ***
Enable dynamic configurations for all builds.
PiperOrigin-RevId: 158420321
|
|
|
|
|
|
|
|
| |
These were accidentally deleted in
https://github.com/bazelbuild/bazel/commit/7dec00574aa91327693f6ba7e90bff5bc834253e.
RELNOTES: None
PiperOrigin-RevId: 158404948
|
|
|
|
|
|
|
|
| |
Instead of passing a client env into the test strategies, use the same
mechansim as --action_env, by depending on the right set of Skyframe nodes that
correspond to client env entries.
PiperOrigin-RevId: 158401670
|
|
|
|
| |
PiperOrigin-RevId: 158397972
|
|
|
|
|
| |
RELNOTES: ctx.expand_make_variables is deprecated.
PiperOrigin-RevId: 158396106
|
|
|
|
|
|
|
| |
This creates a new class BlazeWorkspaceTest, and removes the initCommand method
from BlazeRuntime.
PiperOrigin-RevId: 158396032
|
|
|
|
|
|
|
|
| |
When bootstrapping, we generate a .zip file of generated java classes.
In this CL we add the java_library_srcs targets, that generate the
sources .jar files for bootstrapping.
Change-Id: Ib33edcc6ba996e433eb646a236e5f44c73b63460
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows `new_git_repository` to depend on codebases with
pre-existing `BUILD` files from other tools, or `build/` directories
in case-insensitive file systems.
Fixes #3127
Closes #3142.
PiperOrigin-RevId: 158392078
|
|
|
|
|
|
|
|
|
|
| |
Removed `--local_genrule_timeout_seconds` from the documentation. This option does not exist in the codebase, and is apparently a holdover from internal docs for blaze.
Fixes #3131
Closes #3140.
PiperOrigin-RevId: 158390228
|
|
|
|
|
|
| |
Closes #3030.
PiperOrigin-RevId: 158387165
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the experimental UI is told to rate limit the amount of output
generated, this limit does not include startup messages generated by
the client. Make the test aware of that behaviour by allowing a bit
more output than the UI limit, to take into account the client startup
messages. To keep the test still strict increase the output generated
by the actions a lot, so that the client output is small compared to
what we expect and limit.
PiperOrigin-RevId: 158386698
|
|
|
|
|
|
|
|
|
| |
- Only manually check the timeout if the process wrapper is not used
- Set the timeout correctly; the process API uses milliseconds
- flush the error output stream after writing
- return SIGALRM as exit code for timeout cases
PiperOrigin-RevId: 158374246
|
|
|
|
|
|
|
|
| |
to store Java compilation artifacts. Round-tripping through
JavaCompilationArgs loses dependency information that upstream
compilations use to optimize compile time classpaths.
PiperOrigin-RevId: 158360995
|
|
|
|
|
|
|
|
|
|
|
|
| |
Support disabling javac fallback for actions without a direct
classpath, and only use the 'JavacTurbine' mnemonic for spawns
that require javac-turbine due to annotation processing to make
it easier to collect metrics on that.
Finally, remove --java_header_compilation_direct_classpath now
that it has been productionized and enabled by default.
PiperOrigin-RevId: 158359858
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Follow-up to https://github.com/bazelbuild/bazel/commit/22b85a2a3c79c6f3aef1e0a61e485bb135be4551. This change updates paths and URLs to Bazel docs,
removing the versions/master directory and changing bazel.build/docs to
docs.bazel.build.
For clarification on the convention of the docs site, links referencing
docs.bazel.build/foo.html will be redirected to
docs.bazel.build/versions/master/foo.html. The versions/master directory will
contain the documentation pages pushed from HEAD. Once versioned documentation
is ready, then docs.bazel.build/foo.html will instead be redirected to
docs.bazel.build/x.y.z/foo.html, where x.y.z is the directory for the latest
stable Bazel version.
Follow-ups to this change:
* Add script that will be used by the daily push job that pushes the latest
documentation from HEAD to docs.bazel.build. This script will do the
following:
* Build the Jekyll tree, run jekyll build, and modify the resulting site
tree, moving the docs/ directory into versions/master.
* Add redirects for each of the site pages from the root of the site
to the corresponding page in versions/master.
* This should give us the minimum viable product for the new docs site.
* Add script for cutting a release of the docs and pushing to a new versioned
directory on the docs.bazel.build bucket.
RELNOTES: None
PiperOrigin-RevId: 158347197
|
|
|
|
|
|
|
| |
Fixes #3122.
RELNOTES: bazel query --output package now displays packages from external repository with the format "@reponame//package". Packages in the main repository continue to have the format "package".
PiperOrigin-RevId: 158327492
|
|
|
|
|
|
|
| |
configurable. Add a test for the current behavior of treating an unreadable BUILD file as a package loading error.
RELNOTES: None
PiperOrigin-RevId: 158314187
|
|
|
|
|
|
|
| |
For all declared non-premitive fields, this CL sets each one to null.
RELNOTES: n/na
PiperOrigin-RevId: 158305638
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
py_test cannot find it's data file at runtime. The reason is it's
running in a wrong directory.
The test directory is set to runfiles directory by test-setup.sh, but on
Windows, python binary unzip itself to another temp directory which
test-setup.sh doesn't know.
So let the python stub template switch to the correct runfiles directory
if RUN_UNDER_RUNFILES = 1
Fixed https://github.com/bazelbuild/bazel/issues/3134
Change-Id: If5dbee811330372d86484ebd871ea55d84bc29a8
PiperOrigin-RevId: 158299041
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Don't flush when buffer is a prefix of SHOW_INCLUDES_PREFIX or
sourceFileName
eg. Since we are looking for a line starting with "Note: including file:",
when buffer equals "Note: i", when should not flush the buffer,
but wait until the whole line is read or we are sure they won't match.
Also, we need to reset the buffer after write to out.
Added test for ShowIncludesFilter.java
Change-Id: I58ebd0bfd5a3e2c9973c8bd910e2e5b85a545c21
PiperOrigin-RevId: 158297616
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
a sample project hosted on GitHub.
This depends on pull request #23 in bazelbuild/examples which uploads the C++ sample project.
Staged at:
[]
[]
PiperOrigin-RevId: 158297121
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This depends on pull request #23 in bazelbuild/examples which modifies the tutorial\WORKSPACE and tutorial\ios-app\BUILD files to match this CL.
Staged at:
[]
[]
[]
[]
RELNOTES: None.
PiperOrigin-RevId: 158296117
|
|
|
|
|
|
|
|
|
| |
This requirement was added to PatchTransition in commit e6392cd380fce14d719890c78d5eb2657e8a6cfc.
This also adds tests for ConfigFeatureFlagTransitionFactory's other
behaviors.
RELNOTES: None.
PiperOrigin-RevId: 158294134
|
|
|
|
|
|
| |
RELNOTES: ios_device and ios_test are deprecated. Please use the new testing
rules in https://github.com/bazelbuild/rules_apple instead.
PiperOrigin-RevId: 158290414
|
|
|
|
|
|
|
|
|
|
|
| |
companion project.
This depends on pull request #23 in bazelbuild/examples which uploads the required Java companion project.
Staged at []
RELNOTES: None.
PiperOrigin-RevId: 158287971
|
|
|
|
|
|
|
| |
indicative of the probable cause of the error.
RELNOTES: None.
PiperOrigin-RevId: 158286091
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 158279811
|
|
|
|
|
|
|
|
|
| |
When running bazel_windows_example_test, we don't need to add
--cpu=x64_windows_msys anymore, which means we can test the MSVC version
of Bazel in this test.
Change-Id: I01a2363e383756d57afd8beab20e66024612c8a0
PiperOrigin-RevId: 158279095
|
|
|
|
|
|
| |
previous change.
PiperOrigin-RevId: 158278265
|