| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
We prefer to focus on the web documentation instead.
RELNOTES[INC]: 'blaze doc_ext' command removed.
--
MOS_MIGRATED_REVID=93871336
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=93639664
|
|
|
|
|
|
|
| |
upcoming release.
--
MOS_MIGRATED_REVID=93328637
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Tested on Linux with the following command line:
$ bazel help info-keys | sort | uniq -c
And compared the output before and after.
Fixes #175
--
Change-Id: Ia879796abf6f5b6b5742bfc9574d64fe53a650a3
MOS_MIGRATED_REVID=93127869
|
|
|
|
|
|
|
| |
Further improvements on #167.
--
MOS_MIGRATED_REVID=92459390
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
ActionContextConsumers.
--
MOS_MIGRATED_REVID=91827715
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=91818123
|
|
|
|
|
|
|
| |
Last step in refactoring of Skylark builtin functions.
--
MOS_MIGRATED_REVID=91796746
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=91713784
|
|
|
|
|
|
|
|
|
|
|
| |
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=91405317
|
|
|
|
|
|
|
| |
computing the test environment as early as possible, and passing that along.
--
MOS_MIGRATED_REVID=91388451
|
|
|
|
|
|
|
|
|
|
| |
`bazel help completion` dump all options completion pattern
for each command, giving hints on the format of the completion
residue (e.g., `label`, `path`, `{a,enum}`, ...). This
dump can be used to generate completion scripts.
--
MOS_MIGRATED_REVID=90743024
|
|
|
|
|
|
|
| |
to be sure that no one uses it.
--
MOS_MIGRATED_REVID=90693216
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=89973895
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=89483786
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=89348225
|
|
|
|
|
|
|
| |
native module.
--
MOS_MIGRATED_REVID=89309511
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=89134285
|
|
|
|
|
|
|
| |
concurrently. We update the timing with the maximum elapsed time. This could prevent us from getting the critical path (because another smaller path could mask the critical path), but in practice we do not expect this to happen.
--
MOS_MIGRATED_REVID=89133458
|
|
|
|
|
|
|
| |
shortened.
--
MOS_MIGRATED_REVID=88922152
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Moves pattern resolving logic from TargetPatternFunction.Resolver to
a top level class. Adds a layer of abstraction to the Resolver
implementation enabling it to be backed by either an Environment or
a Graph, for use in SkyFunction evaluation or on-the-fly evaluation,
respectively. Finally, SkyQueryEnvironment#preloadOrThrow now checks
to see if each target pattern exists in the graph, and any that
don't will be resolved on-the-fly.
--
MOS_MIGRATED_REVID=88861201
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=88755217
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=88257621
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=88160544
|
|
|
|
|
|
|
|
| |
e.g.
$ bazel info bazel-bin
--
MOS_MIGRATED_REVID=87943280
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=87821306
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=87728012
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=87717872
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=87714450
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=87712063
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=87596401
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=87513766
|
|
|
|
|
|
|
| |
can be used in their stead.
--
MOS_MIGRATED_REVID=87334648
|
|
|
|
|
|
|
|
|
| |
This environment eagerly preloads the transitive closure of a specified query "universe", and so may not be as efficient as the standard query for limited-scope queries. It is activated when the universe is specified and ordered results are not requested (since it is currently unable to order results).
Tests were modified/added to exercise this environment where deemed interesting. Some ugly hacks were done to add coverage in AbstractQueryTest and friends, because currently even if the full depot is loaded (using //...), individual target patterns most likely won't be present in the graph. A better way to deal with this situation, suggested by felly, is probably to extract target pattern resolution logic to an auxiliary function so that query is able to resolve target patterns without mutating the graph, and then call into the read-only graph with the resolved patterns. That may be done in a follow-up, in which case the "scope" of every query could be //... .
--
MOS_MIGRATED_REVID=87257028
|
|
|
|
|
|
|
| |
Having an error message in path/to/package and //path/to/package resolve to //path/to/package:package was a bit strange.
--
MOS_MIGRATED_REVID=87171051
|
|
|
|
|
|
|
| |
instead of nanoTime. As nanoTime should only be used to compute time differences. To avoid having to pass two long values representing time (And calling twice to Clock.xxx methods per action executed) we compute the wall time by passing a clock and computing the difference from the start nano time.
--
MOS_MIGRATED_REVID=87102963
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=86738858
|
|
|
|
|
|
|
| |
See associated bug for more details.
--
MOS_MIGRATED_REVID=86708715
|
|
|
|
|
|
|
| |
way to test this, because no matter what I do (pipe to a FIFO, run under stdbuf), Blaze doesn't block on outputting there, so I can't interrupt and cause the exception.
--
MOS_MIGRATED_REVID=86114736
|
|
|
|
|
|
|
|
|
| |
move some utility methods to utility class.
The real goal of this CL is to make sure all users of BlazeQueryEnvironment are constructing one through EvaluableBlazeQueryEnvironment#newQueryEnvironment, and not directly. This ensures that alternate implementations of EvaluableBlazeQueryEnvironment will be automatically injected via #newQueryEnvironment.
--
MOS_MIGRATED_REVID=86112439
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
there was an error in the accounting of how many tests were actually
executed vs those that were cached. this was a result of not considering
remotely cached tests when accumulating test results. fix the bug and
add some unit tests to prove out functionality, as well as some
javadoc clarifying functionality.
R=janakr
--
MOS_MIGRATED_REVID=86112421
|
|
|
|
|
|
|
|
|
|
|
| |
BlazeQueryEnvironment that exposes an evaluateQuery method, and also implements the non-LabelVisitor-specific parts of BlazeQueryEnvironment, for other implementations' uses.
Most of the code is just a straight refactoring of BlazeQueryEnvironment into EvaluableBlazeQueryEnvironment (and BlazeTargetAccessor). Ignoring whitespace changes in [] may be your friend for seeing that it's a straight move.
This also allows us to change tests to use QueryCommand.newQueryEnvironment, in preparation for newQueryEnvironment potentially returning a different EvaluableBlazeQueryEnvironment subclass depending on the circumstances.
--
MOS_MIGRATED_REVID=86088953
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=85902304
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
coverage information was being added only if the build wasn't cached
locally, and only if it wasn't attached before. the former was
undesirable as the coverage data is still there and interesting. the
latter prevented information being displayed for sharded tests
note testing for exact coverage file names seems a bit flimsy, but if
the code changes breaking our assumptions it should be simple enough
to catch.
--
MOS_MIGRATED_REVID=85896250
|
|
|
|
|
|
|
| |
exception to blaze.INFO. Otherwise, it's easy to miss the fact that there was an important failure.
--
MOS_MIGRATED_REVID=85760959
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=85722639
|
|
--
MOE_MIGRATED_REVID=85702957
|