| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
I missed these in https://github.com/bazelbuild/bazel/commit/654c77c603c039142d8b257f47bdaf14ac507c47.
RELNOTES: None.
PiperOrigin-RevId: 202706112
|
|
|
|
|
| |
TYPE_CHANGE_OK=Proto hasn't yet been used
PiperOrigin-RevId: 202705882
|
|
|
|
| |
PiperOrigin-RevId: 202704472
|
|
|
|
| |
PiperOrigin-RevId: 202703621
|
|
|
|
|
|
|
| |
un-italicize the rest of the docs.
RELNOTES: None
PiperOrigin-RevId: 202703376
|
|
|
|
|
|
|
| |
objects for Skydoc.
RELNOTES: None.
PiperOrigin-RevId: 202697176
|
|
|
|
|
|
|
|
|
|
| |
This changes the BuildEventArtifactUploader to an async interface,
thereby no longer potentially delaying event delivery over the
eventbus. Additionally, the BES transport is changed to start
uploading local files immediately as the events are delivered.
RELNOTES: None
PiperOrigin-RevId: 202694121
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 202692405
|
|
|
|
| |
PiperOrigin-RevId: 202690640
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 202690562
|
|
|
|
|
|
|
|
|
| |
The "elapsedTimeNanos > 0" conditional is highly likely to always be
true, but if not, the progress receiver won't receive an "ending"
event for the "compute" state.
RELNOTES: None
PiperOrigin-RevId: 202687683
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 202685157
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 202677272
|
|
|
|
|
|
|
|
| |
non-empty set of output files. This would catch a degenerate case when for some
reaon an empty was returned.
RELNOTES: None.
PiperOrigin-RevId: 202672729
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If a SkyFunction read a value (or its absence) from the graph during its
evaluation, that value will be used to compute the event and post
metadata for that evaluation.
This CL modifies the assertion strategy for this code. Previously,
registered deps which were not done would have gone undetected, and
their events/posts skipped.
This CL also makes a few minor changes that make SkyFunctionEnvironment
more consistent:
- Deps not already in previouslyRequestedDepsValues are added to
newlyRequestedDeps regardless of whether evaluation was in
error bubbling or whether the dep was done.
- Previously requested deps of an inflight node are prefetched (by
passing them to SkyFunctionEnvironment's ctor) during error bubbling in
the same way as they are during normal eval or cycle checking.
- Minor signature and documentation adjustments.
RELNOTES: None.
PiperOrigin-RevId: 202672709
|
|
|
|
| |
Change-Id: I1210baa97c9f9bf817f8b26f6a75b7c31da2e48b
|
|
|
|
|
|
|
|
|
| |
If a program `abort`s, `exit`s, or `exec`s a different program,
destructors won't run. To allow RAII in wrapped_clang, remove all its
`abort` and `exec` calls. `main` is now the single exit point for the
program, and destructors will always run after `main` returns.
PiperOrigin-RevId: 202658759
|
|
|
|
|
|
|
|
|
|
| |
This is done so that we can check whether the current target can use the C++
Skylark API.
Rolling forward: BlazeInvocationPolicy is not used in host configuration. We simply ignore host configuration and not give an error when we are building there.
RELNOTES:none
PiperOrigin-RevId: 202652552
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[Rolling forward https://github.com/bazelbuild/bazel/commit/c4e128e2c6d8cacaeba034d6a3195796d50f1745]
java_common.compile doesn't generate the output source jar when a source jar is
the only input for the compilation. This is wrong because the source jar can
include APT generated sources. It is also inconsistent with java_library and
leads to inconsistent Skylark rules where a declared output will not always have a
generating action.
This new behavior is guarded by a new flag --incompatible_generate_javacommon_source_jar.
RELNOTES: None.
PiperOrigin-RevId: 202648346
|
|
|
|
| |
PiperOrigin-RevId: 202644968
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 202644613
|
|
|
|
| |
PiperOrigin-RevId: 202644128
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks tests: b/110978519
*** Original change description ***
C++: Adds ctx to cc_link_params creation.
This is done so that we can check whether the current target can use the C++
Skylark API.
RELNOTES:none
PiperOrigin-RevId: 202643988
|
|
|
|
|
|
|
| |
test packages.
RELNOTES: None.
PiperOrigin-RevId: 202642995
|
|
|
|
| |
PiperOrigin-RevId: 202642497
|
|
|
|
|
|
|
| |
In preparation of removing tools/defaults, I realized that creating empty build file under tools/defaults folder is unnecessary.
RELNOTES:none
PiperOrigin-RevId: 202635096
|
|
|
|
|
|
| |
Closes #5486.
PiperOrigin-RevId: 202634385
|
|
|
|
|
|
|
|
| |
This is done so that we can check whether the current target can use the C++
Skylark API.
RELNOTES:none
PiperOrigin-RevId: 202632582
|
|
|
|
|
|
|
| |
The current logic could fail due to StringIndexOutOfBoundsException because of calling version.substring(0, -1). The system property "java.version" could be a single integer that does not contain dot.
RELNOTES: None
PiperOrigin-RevId: 202578981
|
|
|
|
| |
PiperOrigin-RevId: 202577988
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This ensures that if a SkyFunction read a value (or its absence) for a
dep during its evaluation, subsequent requests for that dep's value (or
its absence) provide the same result.
This does not yet necessarily apply to the process of collecting events
and posts from a node's deps, which will be considered in a future
refactoring.
This CL adds SkyFunctionEnvironment#removeUndoneNewlyRequestedDeps
because the prior strategy for removing undone deps for done parents, by
re-requesting the dep's node from the graph and checking its doneness,
could lead to deps being dropped from parents if those deps transitioned
from done to dirty as the parent completes.
Minor cleanup to the bubbleErrorInfo field, which is nullable, and now
documented.
(Note that done->dirty node transitions during evaluation are planned,
but not yet possible.)
RELNOTES: None.
PiperOrigin-RevId: 202577098
|
|
|
|
|
|
|
|
| |
Closes #5307
Closes #5455.
PiperOrigin-RevId: 202567483
|
|
|
|
|
|
|
| |
Skydoc will generate documentation for all rule definitions in the transitive dependencies of the given input file.
RELNOTES: None.
PiperOrigin-RevId: 202553088
|
|
|
|
|
|
|
| |
directory.
RELNOTES: None.
PiperOrigin-RevId: 202542139
|
|
|
|
|
|
|
| |
These fakes won't behave at all like real implementations at this time. In fact, invoking some of their methods (or accessing their fields) may result in an error. This serves, however, as the initial check-in which can be iterated on and improved later.
RELNOTES: None.
PiperOrigin-RevId: 202525168
|
|
|
|
|
| |
RELNOTES: --[no]allow_undefined_configs no longer exists, passing undefined configs is an error.
PiperOrigin-RevId: 202518987
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
SkyFunctionEnvironment only cares about directDeps' values, not other
NodeEntry data.
This reduces the space of code which could be sensitive to nodes which
transition from done to dirty during evaluation.
To prevent check-then-act races in the refactored code (and only there;
other code will be fixed in future refactorings), instead of checking
deps' isDone() methods before accessing their value, allow
getValueMaybeWithMetadata to be called when not done, and have it return
null when not done.
(Note that done->dirty node transitions during evaluation are planned,
but not yet possible.)
RELNOTES: None.
PiperOrigin-RevId: 202518781
|
|
|
|
| |
PiperOrigin-RevId: 202514441
|
|
|
|
|
|
|
|
| |
The short-circuiting code was pulled into the !keepGoing conditional
block inadvertently.
RELNOTES: None.
PiperOrigin-RevId: 202505510
|
|
|
|
|
|
| |
and avoid needlessly copying lists.
PiperOrigin-RevId: 202504396
|
|
|
|
|
|
|
| |
This will allow us to reuse the code for the action graph query in a later CL.
RELNOTES: None
PiperOrigin-RevId: 202500176
|
|
|
|
|
|
|
|
|
|
| |
This will be enforced by annotation processor.
This will be followed up, along with turndown of mandatoryPositionals, by
removing the intepreter code which infers the correct number and type of parameters.
RELNOTES: None.
PiperOrigin-RevId: 202499089
|
|
|
|
|
|
|
|
| |
This is the first PR for my Arm64 test cleanup.
Closes #5457.
PiperOrigin-RevId: 202492291
|
|
|
|
|
| |
RELNOTES:none:
PiperOrigin-RevId: 202491609
|
|
|
|
|
|
|
|
| |
/cc @vbatts
Closes #5482.
PiperOrigin-RevId: 202489367
|
|
|
|
|
|
|
|
| |
Without this parameter, I was getting the same error that others reported at https://github.com/bazelbuild/migration-tooling/issues/86
Closes #5460.
PiperOrigin-RevId: 202484116
|
|
|
|
|
|
| |
RELNOTES:none
PiperOrigin-RevId: 202483718
|
|
|
|
|
|
|
| |
Closes #5478.
Change-Id: I3ac44605ef16a7c2e6bdc63d26fdf968bef651aa
PiperOrigin-RevId: 202482493
|
|
|
|
|
|
|
|
| |
Make ObjcRuleClasses uses CppRuleClasses.ccToolchainAttribute label resolver.
Mark CppRuleClasses.ccToolchainAttribute with @AutoCodec annotation.
RELNOTES:none
PiperOrigin-RevId: 202479836
|
|
|
|
|
|
|
| |
crosstool to agregate all its together.
RELNOTES:none
PiperOrigin-RevId: 202470052
|