| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129895423
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129889793
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129887102
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, in python executable zip file, the default workspace
name "__main__" conflicts with __main__.py file.
This change fixes it.
Also refactored the bazel_windows_example_test
--
Change-Id: I8b9d64d72335148dba41032ce93643d34670a771
Reviewed-on: https://bazel-review.googlesource.com/#/c/5351
MOS_MIGRATED_REVID=129879570
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a re-submission of commit 99de0d07574f808fee36826289cb1f5c83e3b3e0 (rolled back in commit eff8b365c172b7e904ac6f7bba0c893fed7c91a8) and a few tweaks: - The fix for the bug that caused the rollback (see line 888 in CppModel.java -- we now use addNonCodeInputs() instead of addObjectFiles() to pass in the processed header tokens)
- A few extra assertions
- A test case
- The re-submission of the parts of commit 603b540bbcd7414cd3e2c0b92c1c8985b035e41b that were also rolled back as collateral damage.
The bug report didn't contain a precise reproduction, but the bug is trivial enough that I'm comfortable with things this way.
--
MOS_MIGRATED_REVID=129872117
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129870872
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We don't have to add the stub_template.txt as the python
zip file header except a simple '#!/usr/bin/env python' shebang, because it's
equivalent to 'python <file>'. Apparently, python checks the file
type firstly, if it's a zip file, it will find and run __main__.py
instead of running the header script.
--
Change-Id: Icbd3bacacc3857dc3b857d3a7cb770fd94362b9d
Reviewed-on: https://bazel-review.googlesource.com/#/c/5350
MOS_MIGRATED_REVID=129870674
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129869968
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129867284
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129865689
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129864137
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129863453
|
|
|
|
| |
Change-Id: I1505726ca66ab578cf29d2dc6018a2ff1e2ccaaf
|
|
|
|
|
|
|
|
|
| |
sandbox on Mac and is also not necessary.
Fixes #1625.
--
MOS_MIGRATED_REVID=129860300
|
|
|
|
|
|
|
|
| |
It's never used, and it's tricky to run with multiple different file systems
in the same process -> remove it to simplify.
--
MOS_MIGRATED_REVID=129858142
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129856323
|
|
|
|
|
|
|
| |
This allows us to make the coverage module stateless if it depends on options.
--
MOS_MIGRATED_REVID=129852270
|
|
|
|
|
|
|
|
| |
Closes #1496.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1496
MOS_MIGRATED_REVID=129846158
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129843837
|
|
|
|
|
|
|
| |
Require all callers to call initWorkspace after BlazeRuntime construction.
--
MOS_MIGRATED_REVID=129842292
|
|
|
|
|
|
|
|
|
| |
With this change, dynamic configs are at full feature parity for
split transitions (minus some small differences in composed
transitions from BuildConfigurationCollection.configurationHook).
--
MOS_MIGRATED_REVID=129802414
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Makes blaze unable to build //third_party/stl
IllegalArgumentException: complex.h.processed
at com.google.common.base.Preconditions.checkArgument(Preconditions.java:127)
at com.google.devtools.build.lib.util.Preconditions.checkArgument(Preconditions.java:38)
at com.google.devtools.build.lib.rules.cpp.CppLinkActionBuilder.addObjectFile(CppLinkActionBuilder.java:831)
NOT a clean rollback; conflict in one file (CppCompilationContext.java).
So this also partially rolls back commit 603b540bbcd7414cd3e2c0b92c1c8985b035e41b (just the change in that file).
*** Original change description ***
Cleanup: store non-code inputs to link actions separately.
--
MOS_MIGRATED_REVID=129798636
|
|
|
|
|
|
|
| |
optimization, second attempt.
--
MOS_MIGRATED_REVID=129797456
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129787305
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In stub_template.txt, we now unzip the python zip file to a temp
directory if needed.
This will get rid of bash in python executable file completely.
Users can run the binary directly or using python <zip>, like:
./bazel-bin/examples/py_native/bin
or python ./bazel-bin/examples/py_native/bin
On Windows, we can use the second way to run python binary from native
Windows command line (cmd.exe).
--
Change-Id: I73fdd88f05f8f343dd19b2f3686ae031dfb476ba
Reviewed-on: https://bazel-review.googlesource.com/#/c/5310
MOS_MIGRATED_REVID=129767890
|
|
|
|
|
|
|
| |
use it instead of switch statement in output_jar. Move implementations to combiners.cc
--
MOS_MIGRATED_REVID=129763019
|
|
|
|
|
|
|
|
|
|
|
| |
declaration from the generated manifest if the list of requested densities contains an unsupported density.
Typically, the DensitySpecificManifestProcessor will add a <compatible-screens> declaration with a <screen> element for every density specified in the "densities=" argument of the android_binary build rule. If the "densities=" argument includes a density not officially supported by the Play Store, it will throw an exception and the build will fail.
After this change, an build rule that explicitly specifies a density not officially supported by the Play Store will instead result in the <compatible-screens> declaration being omitted from the generated manifest, indicating that the APK can support all densities.
--
MOS_MIGRATED_REVID=129761968
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129759632
|
|
|
|
|
|
|
|
|
|
|
| |
Bazel users that are using a different Guava version than the one in the
junitrunner jar are getting an IncompatibleClassChangeError. This CL rewrites
parts of junitrunner code so it won't depend on Guava anymore.
Continuing progress on issue #1150. Removed Guava dependencies, except for
Supplier and Ticker, from junit.runner.junit4.
--
MOS_MIGRATED_REVID=129757029
|
|
|
|
|
|
|
| |
CppLinkAction.
--
MOS_MIGRATED_REVID=129753508
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129753109
|
|
|
|
|
|
|
|
|
|
|
| |
experimental_objc_library. Do this by introducing CommandAction, which
contains the common interface of SpawnAction and CppCompileAction needed for
testing.
This change will allow compilation, linking, and archiving tests to be copied over into the experimental tests.
--
MOS_MIGRATED_REVID=129749930
|
|
|
|
|
|
|
| |
These are not mentioned on the linker command line, and as such, are useless.
--
MOS_MIGRATED_REVID=129746593
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129743936
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is done in preparation for allowing multiple workspaces / commands in a
single server. That requires changes to the module API, which currently
hard-codes a 1:1 correspondence between workspaces and servers. Note how
BlazeDirectories exists even when it runs outside a workspace.
It's not ideal that the output base is in ServerDirectories, and the
BlazeRuntime creation also still requires a BlazeDirectories instance.
--
MOS_MIGRATED_REVID=129736613
|
|
|
|
|
|
|
|
|
|
| |
Bazel users that are using a different Guava version than the one in the
junitrunner jar are getting an IncompatibleClassChangeError. This CL rewrites
parts of junitrunner code so it won't depend on Guava anymore.
Starting progress on issue #1150. Removed Guava dependencies from junit.junit4.runner, junit.runner and junit.runner.internal.
--
MOS_MIGRATED_REVID=129735482
|
|
|
|
|
|
|
| |
called at places where a CcToolchainProvider is near so that we can use information in it to infer how each input file is linked.
--
MOS_MIGRATED_REVID=129729628
|
|
|
|
|
|
|
| |
function.
--
MOS_MIGRATED_REVID=129726780
|
|
|
|
|
|
|
|
|
|
|
| |
Only by doing this, we can load shared library from packaged python
binary.
Also fixed some bugs in building python executable zip.
--
Change-Id: I80fb5f99cf06f78b86c3e5de410578a350d31846
Reviewed-on: https://bazel-review.googlesource.com/#/c/4263
MOS_MIGRATED_REVID=129726147
|
|
|
|
|
|
|
|
|
|
|
|
| |
removing unused test case classes.
Also includes the following changes:
Fixes images for design doc "Beautiful Error Messages".
--
MOS_MIGRATED_REVID=129725896
|
|
|
|
|
|
|
| |
change error messages in these cases to not assume there was an execution phase.
--
MOS_MIGRATED_REVID=129723717
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Having a proxy URL defined with a trailing slash caused an exception. `Proxy address ... is not a valid URL"` This pull request fixes this issue.
I also added two test cases for this issue. 1. Trailing slash in proxy URL. 2. No
user:password provided in proxy URL.
Closes #1597.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1597
MOS_MIGRATED_REVID=129721433
|
|
|
|
|
|
|
| |
usable across front-end types.
--
MOS_MIGRATED_REVID=129633711
|
|
|
|
|
|
|
| |
--
Change-Id: Idf232f3dce3a3221d9a35c89dcef13437b0c25ba
Reviewed-on: https://bazel-review.googlesource.com/#/c/3905/
MOS_MIGRATED_REVID=129620348
|
|
|
|
|
|
|
|
|
| |
compiler_files were also added to support link stamping. However, if a
toolchain is used for link stamping, the linker_files should contain the
necessary tools for that.
--
MOS_MIGRATED_REVID=129616826
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Break test //src/test/shell/bazel:linux_sandbox_test
*** Original change description ***
Prefer IP agnostic terms in favor of those only for ipv4.
--
MOS_MIGRATED_REVID=129616589
|
|
|
|
|
|
|
| |
--
Change-Id: I58686bc87be725041e98ed738890e7b0c7294a3b
Reviewed-on: https://bazel-review.googlesource.com/#/c/4261/
MOS_MIGRATED_REVID=129616564
|
|
|
|
| |
MOS_MIGRATED_REVID=129615955
|
|
|
|
|
|
|
| |
--
Change-Id: I49d4bcdb60052a5cf94049f962732ee2167828f1
Reviewed-on: https://bazel-review.googlesource.com/#/c/4300
MOS_MIGRATED_REVID=129615052
|
|
|
|
|
|
|
|
|
| |
another command.
This is kind of lame (better would be to guarantee that once a command is accepted, it will run), but better than just crashing.
--
MOS_MIGRATED_REVID=129606325
|