| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
"blaze test".
RELNOTES: None.
PiperOrigin-RevId: 174386473
|
| |
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 169258065
|
| |
|
|
| |
PiperOrigin-RevId: 168802886
|
| |
|
|
|
|
|
|
|
| |
If there is a build failure, don't clobber the terse test summary
by naming all the (usually many) tests that were skipped due to
this failure.
Change-Id: I6daae3efb1594c2b1018f87a50cf63949a34535b
PiperOrigin-RevId: 166983264
|
| |
|
|
|
|
|
|
| |
These are depended upon by analysis code, so need to live in the same library
as lib.analysis. Moving them here makes it possible to split the build-base
library into separate libraries for analysis, execution, and rules.
PiperOrigin-RevId: 164847161
|
| |
|
|
|
|
|
| |
The option filters proto dependency can be removed from the OptionsParser. This is in response to option parser users that want to avoid the bazel-internal proto file in their dependencies.
RELNOTES: None.
PiperOrigin-RevId: 162249778
|
| |
|
|
|
|
|
|
|
|
| |
When showing the summary of test results on the terminal, for multi-configuration
builds it can happen that the same label occurs twice (as the test was run for
multiple configurations). In this case, also show the configuration (as mnemonics)
for all tests in the summary.
RELNOTES: None
PiperOrigin-RevId: 160875427
|
| |
|
|
|
|
|
|
| |
Move the default from the annotation to every mention. This makes the incompleteness explicit. Will add the defaults to test targets in a separate change.
Once all dependencies are cleaned up, the Option annotation will no longer allow options without the documentationCategory or effectTag, to prevent new options being added without categories while we migrate to the new option categorization.
PiperOrigin-RevId: 160281252
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is part of refactoring test strategy to unify its implementation between
Bazel and Blaze (Google's internal version of Bazel), which should fix several
issues in Bazel.
It's also necessary to untangle lib.rules and lib.exec to enforce proper
layering by separating compilation of these packages, and to provide a minimal
Bazel binary. In particular, no core part of Bazel should depend on any of the
rules, to facilitate moving them out of Bazel / reimplementing them in Skylark
(except for some core rules like test_suite, alias, and genquery).
--
PiperOrigin-RevId: 142151901
MOS_MIGRATED_REVID=142151901
|
| |
|
|
|
|
|
|
|
| |
message.
This fixes the output "Executed 1 out of 1 tests".
--
MOS_MIGRATED_REVID=121949576
|
| |
|
|
|
| |
--
MOS_MIGRATED_REVID=114998075
|
| |
|
|
|
| |
--
MOS_MIGRATED_REVID=109295552
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
--
MOE_MIGRATED_REVID=85702957
|
lberki
ccalvarin
cushon
Klaus Aehlig
ulfjack
Googler
Florian Weikert
Damien Martin-Guillerez
Han-Wen Nienhuys