| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
This requires a fairly large amount of changes to fundamental objects like BlazeRuntime, Executor, and so on, as well as changing a lot of test code to thread the file system through. I expect future CLs to be much smaller.
PiperOrigin-RevId: 173678144
|
|
|
|
|
|
|
|
|
| |
Split collect, concurrent, vfs, windows into package-level BUILD files.
Move clock classes out of "util", into their own Java package.
Move CompactHashSet into its own Java package to break a dependency cycle.
Give nestedset and inmemoryfs their own package-level BUILD files.
PiperOrigin-RevId: 167702127
|
|
|
|
|
| |
RELNOTES: The `print` function now prints debug messages instead of warnings.
PiperOrigin-RevId: 164880003
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rollforward with fix for test flakiness. BEP transport closed
events are delivered via their own threadpool and thus might
not have been sent immediately. BuildEventStreamerTest#testSimpleStream
now waits for a bit until the event has been delivered. I ran the test
with --runs_per_test=1000 several times and had no further failures.
*** Original change description ***
Automated g4 rollback of commit 3d596d63f883fff56001ed7b2e5cf51dba45f082.
*** Reason for rollback ***
Made BuildEventStreamerTest#testSimpleStream 3% flaky based on --runs_per_test=1000.
RELNOTES: None
PiperOrigin-RevId: 154170833
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Made BuildEventStreamerTest#testSimpleStream 3% flaky based on --runs_per_test=1000.
RELNOTES: None
PiperOrigin-RevId: 154090559
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The BEP (build event protocol) upload may at times take longer than the build
itself. This is especially true for cached builds, where there is little build
work, but the protocol still needs to be uploaded. In this case the bazel UI
will now display that it's waiting for BEP upload, both in the current and the
new experimental UI (--experimental_ui).
When executing a run command, blaze waits for the BEP upload to finish before
it runs the target.
Major Modifications:
- The BuildEventTransport interface now also has a name() method that returns
a string. When waiting for a transport to finish the BEP upload, this string
is displayed in the UI.
- The BuildEventStreamer now emits two new events
AnnounceBuildEventTransportsEvent and BuildEventTransportClosed on the event
bus. This is how the experimental UI is informed about BEP upload progress.
RELNOTES: None
PiperOrigin-RevId: 154052401
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With more specific information to be reported by Skyfunctions, e.g.,
to inform the build-event protocol on missing files, the EventHandler
interface is no longer enough. Therefore, provide an enriched context
for reporting events.
--
Change-Id: I2d06166fe4d5b9054e24ad8c752fafc039e3f9f8
Reviewed-on: https://cr.bazel.build/8794
PiperOrigin-RevId: 148463437
MOS_MIGRATED_REVID=148463437
|
|
|
|
|
|
|
| |
usable across front-end types.
--
MOS_MIGRATED_REVID=129633711
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=121116897
|
|
|
|
|
|
|
|
|
|
|
|
| |
versions:
devtools/build/lib/analysis/util/AnalysisTestCase.java
devtools/build/lib/analysis/util/BuildViewTestCase.java
devtools/build/lib/packages/util/PackageLoadingTestCase.java
devtools/build/lib/testutil/FoundationTestCase.java
--
MOS_MIGRATED_REVID=109560679
|
|
|
|
|
|
|
| |
PackageFactoryTest and PackageFactoryApparatus.
--
MOS_MIGRATED_REVID=104094984
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103823555
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=98914983
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=98914195
|
|
|
|
|
|
|
|
| |
One of them moves up to BuildViewTestCase, the other is done as a static
import where needed.
--
MOS_MIGRATED_REVID=98484132
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92241595
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92143534
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92128998
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=91999865
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=91986167
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=91985334
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=91983663
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=91976263
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90984191
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90799686
|
|
|
|
|
|
|
|
|
| |
This allows removing most /[]/ prefixes from all output file names in all
tests that inherit from FoundationTestCase; that, in turn, allows us to switch
the workspace root to a neutral name, such as /workspace/.
--
MOS_MIGRATED_REVID=90720852
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90543040
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=89684460
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=88964412
|
|
|
|
|
|
|
|
| |
methods available doesn't seem to carry its weight, and this makes it easier
for us to migrate to JUnit 4.
--
MOS_MIGRATED_REVID=87597162
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=87595869
|
|
|
|
|
|
|
| |
This is needed for taking the runfiles prefix from the WORKSPACE file instead of hardcoding it.
--
MOS_MIGRATED_REVID=87347883
|
|
|
|
|
|
|
|
|
|
|
|
| |
tree, rewrite most uses of assertPresence. This is a small step towards
migrating the tests to JUnit 4. Depending on inheritance for the assert*
methods is not recommended, and the (old) Asserts class is deprecated in
JUnit 4.
Sorry, there was no good way to do this piecemeal.
--
MOS_MIGRATED_REVID=87154212
|
|
|
|
|
|
|
|
|
|
|
|
| |
While attempting to clean up the Bazel examples, I noticed that the example
tests don't actually work because they expect a third_party directory. We could
link third_party/ from the top-level bazel directory, but then we'd have
crossing symlinks (base_workspace/tools->tools and
third_party->base_workspace/third_party). Linking everything in one direction
seemed like a better option, but alternative suggestions are welcome.
--
MOS_MIGRATED_REVID=86703332
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also includes the following changes:
Skylark: tests copy the Skylark files into the same directory. Load statements are replaced with relative paths within bzl files and with absolute paths in tests.
--
Refactor Objc abstract rule classes.
This new arrangement groups attributes by logical purpose and clarifies
rule composition. For example objc_binary inherits "linking" whereas an
objc_library inherits "linkable" but both inherit "compiling".
The only functional change in this CL is to remove the "data" attribute
from all rules as it is not used in the depot and doesn't make sense
when we also allow specifying resources in any number of other ways.
--
MOS_MIGRATED_REVID=86676190
|
|
--
MOE_MIGRATED_REVID=85702957
|