| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114431043
|
|
|
|
|
|
|
| |
This makes it possible to compile //third_party/ijar with a bootstrapped Bazel on Windows in dslomov's tree.
--
MOS_MIGRATED_REVID=114428109
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114428005
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114372166
|
|
|
|
|
|
|
| |
GraphConcurrencyTest by allowing us to set an initial version, as well as a method to return the version's successor.
--
MOS_MIGRATED_REVID=114367424
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114365733
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
This change broke internal docs and is no longer needed because the
documentation pipeline will automatically take care of converting these to
.html
for the external site.
*** Original change description ***
Fix links in http://bazel.io/docs/skylark/
--
MOS_MIGRATED_REVID=114364411
|
|
|
|
|
|
|
|
|
| |
function. In the case of the requires-darwin tag, /bin/bash will be used instead
of an alternative, which matches the current genrule implementation.
--
MOS_MIGRATED_REVID=114360408
|
|
|
|
|
|
|
| |
recover from errors. In the case of a single keep_going build, with no subsequent nokeep_going builds, storing the errors is unnecessary.
--
MOS_MIGRATED_REVID=114355846
|
|
|
|
|
|
|
| |
Part of this change makes the --no-version-vectors only be propagated if the sdk tools are >= 23.
--
MOS_MIGRATED_REVID=114351246
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114350802
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114344238
|
|
|
|
|
|
|
| |
tests. Replace it in tests with direct Skyframe graph lookups.
--
MOS_MIGRATED_REVID=114335937
|
|
|
|
|
|
|
| |
A small step towards the resolution of #276.
--
MOS_MIGRATED_REVID=114330517
|
|
|
|
|
|
|
| |
--
Change-Id: I7badee212bd05178a30a6ff4c73c8d62258d2c1d
Reviewed-on: https://bazel-review.googlesource.com/#/c/2841
MOS_MIGRATED_REVID=114330213
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114329043
|
|
|
|
|
|
|
|
|
| |
workspace file
Fixes #824.
--
MOS_MIGRATED_REVID=114326952
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114326701
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/blo[]fbbd6a32b95ba746f09dae1eaeaccf675cd5b3/src/main/java/com/google/devtools/build/lib/packages/Attribute.java#L1045
This allows the default value computation for latebound attributes to consider
the values of configurable attributes. This is most directly useful for user-definable Skylark defaults, which have full access to the values of all non-latebound attributes.
Without this change, this kind of scenario crashes Bazel. For example:
------------------
select_rules.bzl:
------------------
def _impl(ctx):
ctx.file_action(
output=ctx.outputs.out_file,
content=ctx.attr.string_value,
)
return struct()
# Bug does not manifest without using this as a default.
def _derived_value(attrs, _):
return Label("//some:dep")
selector_rule = rule(
implementation=_impl,
attrs={
"string_value": attr.string(default=""),
"out_file": attr.output(),
"_derived": attr.label(default=_derived_value),
},
output_to_genfiles=True,
)
def selector_macro(name, out_file="", string_value=""):
# This will fail with selectors.
selector_rule(
name="%s_skylark" % name,
string_value=string_value,
out_file=out_file + ".skylark",
)
# This does not.
native.genrule(
name="%s_genrule" % name,
cmd="echo '" + string_value + "' > $@",
outs=[out_file + ".genrule"],
)
native.filegroup(
name=name,
srcs=[":%s_genrule" % name, "%s_skylark" % name],
)
------------------
BUILD.bzl:
------------------
config_setting(
name = "selector",
values = {"compilation_mode": "opt"},
)
selector_macro(
name = "this_rule",
string_value = """soup? """ + select({
":selector": "no, thank you.",
"//conditions:default": "yes, please!!",
}),
out_file = "this_rule.txt",
)
--
MOS_MIGRATED_REVID=114326474
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch implements distributed caching for Bazel using Hazelcast.
Hazelcast is used as a key value store that stores content of files
indexed by the digest of the file. The cache also stores the list of files
for an action. The key in this case is the digest from the key of the action
and the list of files.
In this change I also added the interface for remote execution. The
implementation will be added in a subsequent patch.
This change is only the first in a series of changes related to distributed
caching and remote execution. I plan to revise the APIs and implementation
in subsequent changes.
--
Change-Id: I569285d6149a4e9f8ba2362682c07a9f1e1943b7
Reviewed-on: https://bazel-review.googlesource.com/#/c/2760/
MOS_MIGRATED_REVID=114325038
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114324917
|
|
|
|
|
|
|
| |
Python sources filegroup was broken by the addition of a new package
--
MOS_MIGRATED_REVID=114323099
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Issue #824 Step 5.
The only thing left to resolve issue #824 are correct handling of
the following cases:
- Forbidding overloading of a repository outside of the first part
of the workspace file (or it will leads to incorrectness issue
and the only use-case is the redefinition of the bazel_tools
repository).
- Better error reporting when trying to refer to a non-existent
repository from the workspace file, for now it will print
a SkyFrame cycle exception.
--
MOS_MIGRATED_REVID=114316464
|
|
|
|
|
|
|
|
|
|
|
| |
directories to PYTHONPATH.
Fixes #702
RELNOTES: Add imports attribute to native Python rules.
--
MOS_MIGRATED_REVID=114314430
|
|
|
|
|
|
|
|
|
| |
parsed Workspace.
Issue #824 Step 4.
--
MOS_MIGRATED_REVID=114314036
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, as of 0c8049f5fc866d785dd83769fa6c38ecf771ba96, these labels
were treated as relative to the repository of the rule in some places
but not others.
From the other commit's message:
They [implicit attribute defaults] now all point to @bazel_tools anyway,
so there is no need [to special-case them].
--
Change-Id: If337eb2579ae613ba09cab0e0c927691922c0a39
Reviewed-on: https://bazel-review.googlesource.com/#/c/2783/
MOS_MIGRATED_REVID=114313341
|
|
|
|
|
|
|
|
| |
The TargetParsingCompleteEvent was posting the post-expansion targets, and the
LoadingPhaseCompleteEvent was missing the test-suite targets.
--
MOS_MIGRATED_REVID=114312273
|
|
|
|
|
|
|
|
| |
Also fix a bug in the LoadingPhaseRunner - we weren't printing an error for
failed targets, duh!
--
MOS_MIGRATED_REVID=114310591
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114304151
|
|
|
|
|
|
|
|
| |
Add a unit test - there is test coverage for this in RunCommandTest, but this
runs much faster.
--
MOS_MIGRATED_REVID=114302062
|
|
|
|
|
|
|
|
|
|
|
| |
The xcodegen script does not yet handle looking for files under @bazel_tools
correctly. This change will let xcode find these targets under the workspace
root, instead of the @bazel_tools repository. Note that this means that the
package path must include third_party/java/j2objc if it does not exist in your
workspace.
--
MOS_MIGRATED_REVID=114268000
|
|
|
|
|
|
|
| |
RELNOTES: Add instrumented file provider support to Skylark rules.
--
MOS_MIGRATED_REVID=114255963
|
|
|
|
|
|
|
| |
RELNOTES[NEW]: cpp configuration does not require objcopy
--
MOS_MIGRATED_REVID=114253655
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114249806
|
|
|
|
|
|
|
|
|
| |
Turbine compiles ijars from source, ignoring method bodies and relaxing error
checks for performance. We can then do normal compilation against those ijars
and move javac off the build's critical path.
--
MOS_MIGRATED_REVID=114247125
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114242270
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the main step toward supporting load statement of remote
repository in the WORKSPACE file (bug #824). Load statement that
refers to a remote repository will depend on the previous fragment
of the workspace file.
Issue #824 Step 3.
--
MOS_MIGRATED_REVID=114237027
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a bit odd - the legacy loading phase runner reports a loading error,
but no target pattern error in keep_going mode, even though it's clearly an
error in the referenced target itself, rather than in its transitive closure.
This happens because the target pattern eval swallows such errors in keep_going
mode, and doesn't even report the error. I tried changing that, but it's a
fairly large refactoring, and that code path is dead if we switch to the new
one.
In the Skyframe-based implementation, both keep_going and nokeep_going paths
now report a target pattern error. (Note that the new code can never report a
loading error, because it doesn't perform transitive loading.)
The corresponding test is moved from SkyframeLoadingAndAnalysisTest to
LoadingPhaseRunnerTest - we don't need any integration test setup for that.
--
MOS_MIGRATED_REVID=114236897
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114234447
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114232294
|
|
|
|
|
|
|
|
| |
Note that this only affects the new Skyframe-based implementation of the
LoadingPhaseRunner, which isn't live yet.
--
MOS_MIGRATED_REVID=114230017
|
|
|
|
|
|
|
| |
build tools version can be used to determine which features to use.
--
MOS_MIGRATED_REVID=114225514
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114223734
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This only applies to interleaved loading and analysis - the production code
is fine.
Add tests for the RedirectChaser, the fdoOptimize code path, the XcodeConfig,
and the Jvm loader. Unfortunately, the configuration factory we internally
create by default contains a mock Jvm loader implementation. Since that is one
Yak too many right now, I'm adding a temporary method to the AnalysisMock.
I added the tests to BuildViewTest for now; technically, they ought to go
into the language-specific test cases, but that would require more refactoring
as those don't currently run with interleaved loading and analysis.
--
MOS_MIGRATED_REVID=114221476
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114217250
|
|
|
|
|
|
|
| |
--
Change-Id: Ifbbda9bb01cd2d7350521183b7754c5004b2ab3d
Reviewed-on: https://github.com/bazelbuild/bazel/pull/862
MOS_MIGRATED_REVID=114213645
|
|
|
|
|
|
|
| |
Fixes #864.
--
MOS_MIGRATED_REVID=114208872
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes the fdo support independent of the configuration, and therefore
safe to cache.
The genfilesPath was only used in AutoFDO builds, which now use the full
exec path to look up profiling data. The profile already refers to imported
files through their full exec paths, so this approach is more consistent.
Furthermore, if we ever have a source file with the same root-relative path as
a generated file, these would conflict in the FdoSupport map, potentially
leading to errors in the build. This may not be possible right now since such
files would conflict in the label namespace and such conflicts are always
resolved towards the generated file.
--
MOS_MIGRATED_REVID=114204994
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114204404
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114202845
|