| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
| |
If --output_groups is specified without a + or a - sign, it removes the
default output groups used for artifact selection from targets.
* Use output_groups=+<group_name> to add an output group,
* Use output_groups=-<group_name> to remove an output group.
--
MOS_MIGRATED_REVID=108247894
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108142169
|
|
|
|
|
|
|
|
|
| |
through to the JVM instead of (almost certainly incorrectly) splitting the options along spaces.
This allows us to pass non-quote-delimited strings to the JVM, which is necessary for things like -XX:OnOutOfMemoryError="kill -3 %p" (normally bash strips those quotes, but they're not stripped when passed via --host_jvm_args).
--
MOS_MIGRATED_REVID=107820087
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107800790
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"DONT_FOLLOW_SYMLINKS_WHEN_TRAVERSING_THIS_DIRECTORY_VIA_A_RECURSIVE_TARGET_PATTERN" will *not* be traversed for transitive target patterns. The motivation here is to allow directories that intentionally contain wonky symlinks (e.g. foo/bar -> foo) to opt out of being consumed by Blaze. For example, given
<workspace>/foo
bar
bad -> .
DONT_FOLLOW_SYMLINKS_WHEN_TRAVERSING_THIS_DIRECTORY_VIA_A_RECURSIVE_TARGET_PATTERN
the 'bad' symlink will *not* be traversed by the pattern '//foo/...'.
--
MOS_MIGRATED_REVID=107738930
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107582017
|
|
|
|
|
|
|
|
|
| |
The loading phase runner is now always created by the SkyframeExecutor, and
the duplicate test is dropped in favor of subclassing and overriding one
method.
--
MOS_MIGRATED_REVID=107188756
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106961863
|
|
|
|
|
|
|
| |
More testing required before we even add a command-line option.
--
MOS_MIGRATED_REVID=106922350
|
|
|
|
|
|
|
|
| |
This is in preparation for adding a Skyframe-based implementation that uses
the recently added TargetPatternPhaseFunction.
--
MOS_MIGRATED_REVID=106920157
|
|
|
|
|
|
|
|
| |
It's unclear if the method is still necessary with Skyframe, but I don't want
to investigate in detail right now.
--
MOS_MIGRATED_REVID=106838896
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106836859
|
|
|
|
|
|
|
|
| |
This only affects tests that previously set a Reporter on the BlazeRuntime;
the production code is already using the per-command Reporter in all cases.
--
MOS_MIGRATED_REVID=106820846
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, if the first run failed (in iteration order, which I don't
think is necessarily execution order) then
--runs_per_test_detects_flakes would report FAILED instead of FLAKY.
--
Change-Id: Ice7889d46203e1598d94a4e3c0bcbe13a45b0fe1
Reviewed-on: https://bazel-review.googlesource.com/#/c/2210/
MOS_MIGRATED_REVID=106693725
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105841866
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105841398
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105840775
|
|
|
|
|
|
|
| |
Preparation for running multiple commands in parallel.
--
MOS_MIGRATED_REVID=105840167
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105499267
|
|
|
|
|
|
|
|
| |
Re-adds the missing execution phase statistics which got lost in the
recent ProfileCommand refactoring.
--
MOS_MIGRATED_REVID=105340677
|
|
|
|
|
|
|
|
| |
Add the --combine option to produce a single aggregated statistics output for
multiple profile files. Outputs neither Skylark histograms nor the task chart.
--
MOS_MIGRATED_REVID=105051164
|
|
|
|
|
|
|
| |
namespace of the WORKSPACE file.
--
MOS_MIGRATED_REVID=104952808
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104865475
|
|
|
|
|
|
|
|
| |
Does not change the default output, but allows reuse of PhaseText
without outputting those statistics.
--
MOS_MIGRATED_REVID=104653246
|
|
|
|
|
|
|
| |
omitting the Gantt-style charts of all tasks and --[no]histograms to omit Skylark histograms which require adding huge amounts of data to the output. Especially necessary when combining data from multiple profile files.
--
MOS_MIGRATED_REVID=104646190
|
|
|
|
|
|
|
|
| |
Options allow displaying some tasks in more detail, e.g. for inspecting what
exactly a Skylark user-defined function calls and how long that takes.
--
MOS_MIGRATED_REVID=104505599
|
|
|
|
|
|
|
|
|
|
| |
This is the new conventions for Copyrights line and some were missed in the previous change.
Generated by:
find -type f -exec sed -i -E 's/Copyright 201([54]) Google Inc/Copyright 201\1 The Bazel Authors/' '{}' ';'
--
MOS_MIGRATED_REVID=104189975
|
|
|
|
|
|
|
|
| |
Also change the semantics to create a new one on every call; inject the offset
where we were previously relying on hidden state in the SkyframeExecutor.
--
MOS_MIGRATED_REVID=104188580
|
|
|
|
|
|
|
|
|
|
| |
The loadingPhaseRunner is stateless, and moving it prevents accidentally
adding state to it. The TargetPatternEvaluator is not stateless, but is
currently retained by the SkyframePackageManager, so we still keep that state
across invocations (see follow-up CL).
--
MOS_MIGRATED_REVID=104187659
|
|
|
|
|
|
|
| |
--invocation_policy startup flag and allows an application invoking Bazel to set or override flag values (whether from the command line or a bazelrc).
--
MOS_MIGRATED_REVID=104160290
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104102106
|
|
|
|
|
|
|
| |
Remove a lot of now-unused Reporter parameters.
--
MOS_MIGRATED_REVID=104100061
|
|
|
|
|
|
|
| |
It seems unused, and the Bazel dashboard is more useful, as can persist results.
--
MOS_MIGRATED_REVID=104085798
|
|
|
|
|
|
|
|
|
| |
It doesn't contain any state anymore, so creating a new instance per command
is safe. On the other hand, it would be just as safe to merge the remaining
code into SkyframeBuildView, which we might do in the future.
--
MOS_MIGRATED_REVID=104010694
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104008237
|
|
|
|
|
|
|
|
|
|
|
| |
The headers were modified with
`find . -type f -exec 'sed' '-Ei' 's|Copyright 201([45]) Google|Copyright 201\1 The Bazel Authors|' '{}' ';'`
And manual edit for not Google owned copyright. Because of the nature of ijar, I did not modified the header of file owned by Alan Donovan.
The list of authors were extracted from the git log. It is missing older Google contributors that can be added on-demand.
--
MOS_MIGRATED_REVID=103938715
|
|
|
|
|
|
|
| |
RELNOTES:
--
MOS_MIGRATED_REVID=103869828
|
|
|
|
|
|
|
| |
Removes mutable global state.
--
MOS_MIGRATED_REVID=103837106
|
|
|
|
|
|
|
|
|
| |
Instead, pass an appropriate EventHandler instance in. This is in preparation
for creating a per-command EventHandler, in preparation for allowing multiple
commands to run in parallel. This is removal of shared global state.
--
MOS_MIGRATED_REVID=103828963
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103744520
|
|
|
|
|
|
|
|
| |
Also move ownership of ArtifactFactory to SkyframeBuildView; simplify the
code.
--
MOS_MIGRATED_REVID=103722228
|
|
|
|
|
|
|
| |
and enable their reuse
--
MOS_MIGRATED_REVID=103634406
|
|
|
|
|
|
|
|
|
|
| |
- Label parsing can be simplified
- lib.syntax is only contains the code for Skylark and is reasonably independent from the problem domain of building things
This change is mostly only changes to imports declarations. The rest is reversing the dependency between :cmdline and :syntax and moving a tiny amount of code between Printer and FilesetEntry and the addition of SkylarkPrintableValue that I couldn't be bothered to separate out into its own change.
--
MOS_MIGRATED_REVID=103527877
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103376668
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103374106
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103367814
|
|
|
|
|
|
|
|
|
|
| |
This change makes it so commands are no longer both stored in the BlazeRuntime
and in the BlazeCommandDispatcher. Instead, they are only stored in
BlazeRuntime and usually passed there during construction. We have some tests
where this is tricky, so I'm keeping the old code path for now.
--
MOS_MIGRATED_REVID=103364581
|
|
|
|
|
|
|
|
| |
They are usually on the same line, so doing this in separate changes can cause
merge conflicts.
--
MOS_MIGRATED_REVID=103362797
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103290841
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I was persuing the idea that BuildView could become stateless. While that
should be possible, we're currently still relying on minimal state in
BuildView (from tests at least) in a way that makes it tricky to remove.
Instead, I'm now trying to move the BuildView into CommandEnvironment, and
create a new one as needed (only for build commands); that makes it safe in the
presence of concurrently running commands, as long as they don't use the same
BuildView instace. (Of course, allowing commands to run concurrently will need
more changes outside of BuildView.)
--
MOS_MIGRATED_REVID=103279370
|