| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107624290
|
|
|
|
|
|
|
|
|
| |
configuration transition *before* trimming the options. This
is because the transition may read fragments that aren't
in the dep itself.
--
MOS_MIGRATED_REVID=107624186
|
|
|
|
|
|
|
| |
old name.
--
MOS_MIGRATED_REVID=107611961
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
trim the BuildOptions to only those needed by the fragment.
This guarantees that the same fragment only gets instantiated
once (for example: we don't want to have two copies of a
CppConfiguration because one copy had PythonOptions and the
other didn't).
This also prevents crashes, e.g. in the Preconditions check in
CcLibraryHelper.addDeps.
--
MOS_MIGRATED_REVID=107609270
|
|
|
|
|
|
|
| |
Otherwise we have potential correctness and performance problems on a missing Skylark import dep.
--
MOS_MIGRATED_REVID=107605200
|
|
|
|
| |
MOS_MIGRATED_REVID=107604619
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for dynamic configurations.
In short, as a configuration gets passed down its dependency tree it's
likely to lose fragments. For example, when a java_library depends on a cc_library,
the former has both JavaConfiguration and CppConfiguration while the latter
only has CppConfiguration.
It's still the "same" configuration in both cases, it's just that it got trimmed.
This cl provides a looser concept of BuildConfiguration equality that
accounts for this.
--
MOS_MIGRATED_REVID=107598262
|
|
|
|
|
|
|
|
|
| |
Fixes #445, based on https://github.com/bazelbuild/bazel/compare/master...ulfjack:cpp-include-path.
RELNOTES: C++ libraries no longer need includes = ["."] (or similar copts) to include paths relative to a remote repository's root.
--
MOS_MIGRATED_REVID=107593486
|
|
|
|
|
|
|
| |
class, in preparation for calling it from Aspects.
--
MOS_MIGRATED_REVID=107587682
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107582017
|
|
|
|
|
|
|
| |
The "clean" command that is run after each shell test finishes (in the tear_down method of test-setup.sh) tries to remove all subdirectories of the output base. This includes the bazel-sandboxes directory. This, however is already being cleaned up continuously in the background by a thread pool setup in SandboxModule. By waiting for the pool to finish before the clean command runs, the race condition can be solved.
--
MOS_MIGRATED_REVID=107578302
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107528918
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107492955
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107484803
|
|
|
|
|
|
|
| |
The -X option removes UID/GID information from the zip file, which of course is non-hermetic. There is still some weirdness with install_base_key, but I couldn't figure out what that is: the files that are checksummed are always the same and they are in the same order.
--
MOS_MIGRATED_REVID=107484288
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107483083
|
|
|
|
|
|
|
| |
This makes all tool dependencies be under @bazel_tools again (and not //tools)
--
MOS_MIGRATED_REVID=107482585
|
|
|
|
|
|
|
| |
instead.
--
MOS_MIGRATED_REVID=107480889
|
|
|
|
|
|
| |
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/571
MOS_MIGRATED_REVID=107471259
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107465479
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107464729
|
|
|
|
|
|
|
|
|
| |
replacing MemoizingEvaluator#getValues et al with WalkableGraph usage. I initially attempted to do this but punted once I realized how much work it would be.
Also make DirectoryListingStateValue and FileStateValue public for use in outside callers of FilesystemValueChecker.
--
MOS_MIGRATED_REVID=107447425
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Any Package name starting with a blacklisted prefix is treated as a deleted package.
Note the relation to prior art in Blaze:
1. Deleted packages indicates to Blaze to pretend certain packages do not exist. The deleted packages are passed in as fully resolved package names. This is important because the invalidation logic when these values changes references the exact package names, as opposed to prefix patterns.
2. Negative patterns in target parsing. (eg, "foo/..., -foo/bar/..."). Note that if //foo:biz depends on //foo/bar:bang, we still visit that dependency. In other words, the negative patterns just control the target pattern parsing, but not the later evaluation of those targets.
Blacklisting acts like both (1) and (2), but in the form of a Precomputed injected value (so modifying the value would be more expensive than modifying deleted_packages).
--
MOS_MIGRATED_REVID=107431993
|
|
|
|
|
|
|
| |
Without this change, an output xcode project artifact refers to the additional sources of its dependency projects, but does not necessarily mark these sources as action inputs.
--
MOS_MIGRATED_REVID=107428634
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107420673
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107416625
|
|
|
|
|
|
|
| |
later evaluation.
--
MOS_MIGRATED_REVID=107406133
|
|
|
|
|
|
|
|
|
|
|
| |
of configuration over to the apple package.
This moves a small number of configuration items over. Future changes will mostly likely follow to move yet more items.
The split here is necessary as it is not only objc-related rules which require information about apple platforms and configuration -- cc rules will need this information as well to
pass appropriate args to clang.
--
MOS_MIGRATED_REVID=107396114
|
|
|
|
|
|
|
| |
Mostly reuses the interpreters argument checking and helper functions.
--
MOS_MIGRATED_REVID=107395974
|
|
|
|
|
|
|
| |
getCheckDepsProtoSources(), to get any indirect sources from alias library cases.
--
MOS_MIGRATED_REVID=107395192
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107394025
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107391382
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107389651
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107389541
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107388016
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107385205
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107379557
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107379349
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107378197
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107378107
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107377319
|
|
|
|
|
|
|
|
| |
Add EvalExceptions for cases in which the interpreter would throw them
during evaluation of the function definition.
--
MOS_MIGRATED_REVID=107376021
|
|
|
|
|
|
|
|
| |
Aspect => ConfiguredAspect
AspectWithParameters => Aspect
--
MOS_MIGRATED_REVID=107375211
|
|
|
|
|
|
|
| |
This should fix the build on Bazel CI.
--
MOS_MIGRATED_REVID=107268744
|
|
|
|
|
|
|
|
|
| |
Replace uses of $SDKROOT and $DEVELOPER_DIR values in compile paths with __DEVELOPER_DIR__ and __SDKROOT__ to that xcrunwrapper can deal with them appropriately.
RELNOTES:none
--
MOS_MIGRATED_REVID=107259512
|
|
|
|
|
|
|
|
|
| |
a sparse array with holes. This appears to be due to the sub shell launching of the tests. By using FUNCNAME as our count of stack frames, and "ignoring" the holes, we get much better stack output on the Mac. Previously we were just erroring out.
RELNOTES:none
--
MOS_MIGRATED_REVID=107255705
|
|
|
|
|
|
|
|
|
| |
is currently limited to compile actions started by the objc_* rules. Adding this because Xcode needs full paths to files embedded in the debug information if you want to debug while running in the simulator.
RELNOTES:none
--
MOS_MIGRATED_REVID=107253500
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the new Skyframe-based loading phase runner as well as with
--experimental_interleave_loading_and_analysis, we no longer run a full loading
phase to load all dependencies; instead, we load packages during configuration
creation and analysis. In that case, the loading phase result's package roots
are empty.
This change should be safe - the analysis package roots can be a subset of the
loading package roots (we may not need to load stuff if there are select
expressions with unused branches for the current set of options), but it should
cover everything that is needed for the execution phase.
If there is a bug in the new code path, it manifests as odd file not found
errors during action execution, where the files seem to be there (but are not
mapped into the exec root due to missing symlinks).
The old code path uses TransitiveTargetValue.getTransitiveSuccessfulPackages(),
the new one uses ConfiguredTargetValue.getTransitivePackages() and
AspectValue.getTransitivePackages(). I audited the new code paths, and they
look ok.
--
MOS_MIGRATED_REVID=107252220
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107249788
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107247614
|