| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
| |
hash code implementation from super class.
--
MOS_MIGRATED_REVID=94297315
|
|
|
|
|
|
|
|
| |
This allows you to use @repo//... syntax outside of the WORKSPACE file, which
makes it easier to use external dependencies.
--
MOS_MIGRATED_REVID=94275085
|
|
|
|
|
|
|
| |
thread pool.
--
MOS_MIGRATED_REVID=94236393
|
|
|
|
|
|
|
|
|
|
|
|
| |
So that a subsequent commit can take advantage of semantic information
known only after target patterns have been parsed, this commit moves
parsing from pattern evaluation time to pattern key construction time.
This leads toward more efficient processing of target patterns in
target pattern sequence evaluation.
--
MOS_MIGRATED_REVID=94025646
|
|
|
|
|
|
|
|
|
|
|
|
| |
RecursivePkgFunction now expects both a rooted path to load packages
beneath and a set of paths to exclude. This also augments existing
machinery to deliver this set of paths to exclude.
This leads toward more efficient processing of target patterns in
target pattern sequence evaluation.
--
MOS_MIGRATED_REVID=94020331
|
|
|
|
|
|
|
|
| |
There were two TargetPattern types, one in cmdline and one in skyframe.
This made things more confusing than they needed to be.
--
MOS_MIGRATED_REVID=94005358
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=93901785
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=93881974
|
|
|
|
|
|
|
|
| |
Some simple logging to tell us what strategy we are using and how many
files we detect as modified. Useful for debugging slow (or fast) builds.
--
MOS_MIGRATED_REVID=93745644
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=93647914
|
|
|
|
|
|
|
|
|
| |
due to configurations.
RELNOTES:
--
MOS_MIGRATED_REVID=93543318
|
|
|
|
|
|
|
| |
different attributes, to which we have attached aspect.
--
MOS_MIGRATED_REVID=93412457
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92944321
|
|
|
|
|
|
|
|
| |
I noticed, while writing http://bazel.io/docs/cpp.html#including-external-libraries-an-example,
that the BUILD file didn't get reparsed when it changed. This fixes that.
--
MOS_MIGRATED_REVID=92921670
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This command takes a one or more targets and fetches any external repository
prerequisites that will be needed to build them.
Example usage:
bazel fetch //foo:bar
If //foo:bar depends on, say, a maven_jar, it'll be downloaded.
--
MOS_MIGRATED_REVID=92279626
|
|
|
|
|
|
|
|
|
| |
1. Make --analysis_warnings_as_errors a no-op.
2. Stop doing a sanity check that we didn't succeed in analysis even with errors emitted.
3. As a result, emit an error about shared actions to the proper listener.
--
MOS_MIGRATED_REVID=92262247
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As far as I can tell, the dependency on the BuildConfigurationCollection node
is not required anymore. The BuildConfiguration is part of the SkyKey, and it
uses object identity.
This shouldn't affect garbage collection due to the explicit
BuildView.dropConfiguredTargets. If we change that in the future, we will have
to be (even more) careful.
--
MOS_MIGRATED_REVID=92134490
|
|
|
|
|
|
|
|
|
| |
Instead of passing BuildConfigurationKey instances around, just pass in the
little data we actually need. This allows removing the BuildConfigurationKey
class.
--
MOS_MIGRATED_REVID=91865340
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of computing flags based on the configuration in two places, we pass
in the configuration and let the common code figure it out.
Also change it so each CT only depends on the build info collection for its
specific configuration. This should be safe, as the API doesn't allow passing
a configuration in - it instead takes ruleContext.getConfiguration, which
should be consistent with the dependency declarations in SkyframeBuildView in
all cases.
--
MOS_MIGRATED_REVID=91819844
|
|
|
|
|
|
|
| |
[]TESTED: See
--
MOS_MIGRATED_REVID=91816612
|
|
|
|
|
|
|
| |
Last step in refactoring of Skylark builtin functions.
--
MOS_MIGRATED_REVID=91796746
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=91642690
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=91605508
|
|
|
|
|
|
|
|
|
|
|
| |
BuildConfiguration.Options.testEnvironment instead of special-casing it in a large number of classes.
The variables in the client environment are read in BlazeRuntime#beforeCommand() now.
Note that this entails a slight loss of caching: before, "--test_env=a=A,b=B" and "--test_env=b=B,a=A" were equivalent, now they are not, since instead of comparing Map<String, String>, List<Map.Entry<String,String>> instances are compared.
--
MOS_MIGRATED_REVID=91570828
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=91407816
|
|
|
|
|
|
|
| |
computing the test environment as early as possible, and passing that along.
--
MOS_MIGRATED_REVID=91388451
|
|
|
|
|
|
|
| |
typically small, the current default is too high.
--
MOS_MIGRATED_REVID=91225981
|
|
|
|
|
|
|
| |
metadata handlers, we can just unconditionally discard all output metadata with this call.
--
MOS_MIGRATED_REVID=91008004
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=91007686
|
|
|
|
|
|
|
|
|
| |
they have started executing in SkyframeActionExecutor.
We were updating the action cache for both actions in this case, but one of the actions' metadata handler was not updated during execution, and thus it had no metadata for outputs.
--
MOS_MIGRATED_REVID=90993813
|
|
|
|
|
|
|
| |
modifications. While there could be bogus targets that modify symlinks, Bazel has output symlinks that point to source code.
--
MOS_MIGRATED_REVID=90827597
|
|
|
|
|
|
|
| |
counters.
--
MOS_MIGRATED_REVID=90749273
|
|
|
|
|
|
|
| |
Note that we probably want to change the discardMetadata signature to no longer take an argument, since we have per-action metadata handling. However, I'd like to know that that's the source of the crash, if it is, which is why I'm not removing the argument right now.
--
MOS_MIGRATED_REVID=90712991
|
|
|
|
|
|
|
| |
Some care was taken to make sure that we only log when a file is missing *after* the action is executed, when its failure to be present should force a build failure anyway, in order to avoid a source of memory pressure.
--
MOS_MIGRATED_REVID=90682557
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90574562
|
|
|
|
|
|
|
|
|
|
|
| |
ActionInputFileCache when given a digest to do a reverse lookup so that metadata can be more easily retrieved.
Discovered inputs are no longer ever put into SingleBuildFileCache, so it is safe to roll this forward now
Because of code changes (meant to ensure the safety of this change), there were conflicts that had to be manually resolved.
--
MOS_MIGRATED_REVID=90425783
|
|
|
|
|
|
|
| |
functionality is gone.
--
MOS_MIGRATED_REVID=90289916
|
|
|
|
|
|
|
| |
the fact that a valid Target exists, and instead request it directly from its Package.
--
MOS_MIGRATED_REVID=90107670
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90081310
|
|
|
|
|
|
|
|
|
|
|
|
| |
The goal of this change is to provide a means for disallowing
files outside of declared, known locations in order to better
enforce the hermeticy and in turn reproducability of builds.
Previously when encountering these files (typically via external
symlinks) we would add a dependency on build_id, now we can
optionally fail the build.
--
MOS_MIGRATED_REVID=90015665
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This introduces a single SkyFunction that has the desired side effect
of loading matching targets and their transitive dependencies in the
graph.
It replaces the two calls to buildDriver.evaluate that made sure the
graph loaded the necessary values before query evaluation with just one
call.
--
MOS_MIGRATED_REVID=89864338
|
|
|
|
|
|
|
| |
and fail hard in other cases.
--
MOS_MIGRATED_REVID=89720528
|
|
|
|
|
|
|
|
|
|
|
| |
for them can be retrieved with other inputs, avoiding a restart.
This also allows us to delete the UndeclaredInputsHandler, since we eagerly cache metadata before entering any ActionCacheChecker methods.
This should also allow us to split FileAndMetadataCache into two separate classes, as well as asserting that SingleBuildFileCache only sees non-artifact ActionInputs. To be done in follow-ups.
--
MOS_MIGRATED_REVID=89718712
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=89713328
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=89704303
|
|
|
|
|
|
|
|
|
| |
for allowing it to be restarted in case of missing deps.
Note that this means that action-cache writing is no longer part of the ACTION_COMPLETE profiling unit.
--
MOS_MIGRATED_REVID=89702039
|
|
|
|
|
|
|
| |
This bug, and all of them like it, will be fixed in an upcoming cl that makes sure all input metadata is obtained through Skyframe. But I think we should have this fix now.
--
MOS_MIGRATED_REVID=89540265
|
|
|
|
|
|
|
|
|
|
| |
Here we additionally identify artifacts as orphaned if they are only
inputs to middleman actions whose outputs are unused. The middleman
actions are still part of the action graph, but we tolerate their
inputs being orphaned.
--
MOS_MIGRATED_REVID=89512745
|
|
|
|
|
|
|
| |
chains.
--
MOS_MIGRATED_REVID=89511018
|
|
|
|
|
|
|
| |
these two versions of query consistent we need to add additional edges to the target that contains aspects, instead of adding it to the target that was in direct deps of the original one.
--
MOS_MIGRATED_REVID=89483301
|