| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
given application as there are cases where you want both.
--
MOS_MIGRATED_REVID=116998425
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116990273
|
|
|
|
|
|
|
|
|
|
| |
srcs instead of throwing an error.
Implicit exporting of the deps of an android_library rule that doesn't have srcs
is deprecated and will soon be removed.
--
MOS_MIGRATED_REVID=116988446
|
|
|
|
|
|
|
| |
...so the docs show up on hover in an IDE.
--
MOS_MIGRATED_REVID=116986129
|
|
|
|
|
|
|
|
|
| |
Kudos to @tfarina for pointing out this dead function declaration.
An older commit (prior to bazel being open sourced) moved the file out of blaze_util.cc but forgot to delete the function declaration from the header file. And a subsequent change (also before bazel was open sourced) renamed/moved the implementation to a place that is now internal-only.
--
MOS_MIGRATED_REVID=116980458
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116980421
|
|
|
|
|
|
|
|
|
| |
Also added correct equals and hash for the SkylarkPath class.
Fixes #1015.
--
MOS_MIGRATED_REVID=116979400
|
|
|
|
|
|
|
| |
(especially with sharding).
--
MOS_MIGRATED_REVID=116975152
|
|
|
|
|
|
|
| |
It has been made obsolete by java_toolchain.jvm_flags.
--
MOS_MIGRATED_REVID=116884961
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Skylark rule context object has a runfiles method. This adds two
optional parameters to that method, "symlinks" and "root_symlinks",
that expose functionality from the underlying Runfiles java class.
With this functionality, one can construct links in the runfiles tree
where the source and destination of the link have different names
and/or relative directories. This might be useful for things like
AppEngine rules where a file in a subdirectory of the source tree
needs to appear in the root directory of the runfiles tree.
If either new parameter is used, the runfiles is subject to stricter
validity checking. This checking propagates to other runfiles that
depend on it.
RELNOTES: Added "root_symlinks" and "symlinks" parameters to Skylark
runfiles() method.
--
MOS_MIGRATED_REVID=116879064
|
|
|
|
|
|
|
| |
Simplify automatic entries creation.
--
MOS_MIGRATED_REVID=116866524
|
|
|
|
|
|
|
| |
OutOfMemoryError and have the JVM send Bazel a SIGUSR2 when it detects an OOM. This should help in certain pathological cases when Bazel GC thrashes for some time after an OOM has been detected.
--
MOS_MIGRATED_REVID=116819359
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This functions was introduced by commit bf98f39d5d69: "Add the ability
to customize the bazel client's...", but at that time it didn't update
EnsureCorrectRunningVersion() function, that uses unlink() function, to
use DeleteFile() as well.
So this patch updates EnsureCorrectRunningVersion() to make use of it
now.
While there is nothing wrong with the current name, it is not very much
correct from the documentation point. If the path is a symlink, unlink()
will just the symbolic link and the file won't be removed (affected at all).
Otherwise, if it is just a normal file, it will just decrement the link
count of the file and when that count reaches zero (0) then the file
will longer be accessible.
So while at it we renamed the function to UnlinkPath(), but could just
stay as DeleteFile() if we wanted.
In this process we also improved the documentation for this function to
be a little more clear and removed moved it from the source file, since
the header file already has it.
For further reference, adhere to the documentation in
http://pubs.opengroup.org/onlinepubs/009695399/functions/unlink.html.
--
Change-Id: I0fc569f3324322cbc67a8fb540836c127f5c3399
Reviewed-on: https://bazel-review.googlesource.com/#/c/3061/
MOS_MIGRATED_REVID=116769254
|
|
|
|
|
|
|
| |
execution are reported. Previously, we would not report the error unless the build was already failing and this error ended up being the root cause of the first failed top-level target.
--
MOS_MIGRATED_REVID=116767915
|
|
|
|
|
|
|
|
|
| |
Adds //third_party/java/j2objc:jre_emul.jar target, needed for a future update
to j2objc_library.
RELNOTES: J2ObjC updated to 1.0.1 release.
--
MOS_MIGRATED_REVID=116767453
|
|
|
|
|
|
|
|
|
|
| |
For backwards compatibility reasons, resources show up in both the
originating rule as well as the containing rule. Implementations can
check the :resources attribute to see if they should ignore their
resources.
--
MOS_MIGRATED_REVID=116698804
|
|
|
|
|
|
|
| |
fully implemented but still being guinea pigged.
--
MOS_MIGRATED_REVID=116694206
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116693888
|
|
|
|
|
|
|
| |
-all_load does not work like whole-archive in the Apple linker. It affects *all* arguments, before and after it. Therefore, a single always_link dependency in a cc_binary on Apple platforms turns *everything* into always_link.
--
MOS_MIGRATED_REVID=116674199
|
|
|
|
|
|
|
|
|
| |
hasattr() when being called with the name of an existing method.
While hasattr(obj, 'existing method') continues to return true, getattr(obj, 'existing method') always throws an exception (with a more detailed message than before), regardless of whether a default value was specified or not.
--
MOS_MIGRATED_REVID=116613716
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116595467
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116593165
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116591761
|
|
|
|
|
|
|
|
|
| |
A runfile conflict is when two different artifacts have been added to a
Runfiles object under the same relative path. Conflict resolution is
unchanged (last artifact wins).
--
MOS_MIGRATED_REVID=116584195
|
|
|
|
|
|
|
|
|
| |
all packages were successful.
Also add Preconditions check to ensure we get the expected Package response when retrieving packages in bulk when we know the set of Package identifiers correspond to valid packages.
--
MOS_MIGRATED_REVID=116580093
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116573891
|
|
|
|
|
|
|
|
|
| |
and specify --experimental_android_resource_shrinking on the command line.
RELNOTES: Specifying --experimental_android_resource_shrinking on the command line will enable a resource shrinking pass on android_binary targets that already use Proguard.
--
MOS_MIGRATED_REVID=116572863
|
|
|
|
|
|
|
| |
Will need to release before we can remove resources from objcbinary rules.
--
MOS_MIGRATED_REVID=116571890
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116569594
|
|
|
|
|
|
|
| |
Bazel exit more eagerly due to an OOM will be guarded by this flag.
--
MOS_MIGRATED_REVID=116567102
|
|
|
|
|
|
|
| |
save memory. This is a partial rollback of f745e99db7632cfb2145b6926f961e85f9084bc5, but that part of the change was unnecessary -- we are already ensuring that an element isn't added twice in GroupedListHelper#add by adding it to elements.
--
MOS_MIGRATED_REVID=116560479
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116553978
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116549753
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116511350
|
|
|
|
|
|
|
| |
that it can depend on Skylark rule.
--
MOS_MIGRATED_REVID=116385078
|
|
|
|
| |
MOS_MIGRATED_REVID=116363666
|
|
|
|
|
|
|
|
|
| |
The shell.Command class throw an exception when exit code is non
null, resulting in unwanted case where calling a failing command
as just echoing "Exited with status 4".
--
MOS_MIGRATED_REVID=116361594
|
|
|
|
|
|
|
|
|
|
|
|
| |
Events may reach the UI over the event bus simultaneously or
with very small time difference. Updating the UI on the terminal,
however is an expensive operation. So update the UI only once
for simultaneous events.
--
Change-Id: I3e6881f18b37626f6be3ad7b97043b42773812f3
Reviewed-on: https://bazel-review.googlesource.com/#/c/3047
MOS_MIGRATED_REVID=116352143
|
|
|
|
|
|
|
| |
count and possibly use that value to make dynamic decisions around scheduling.
--
MOS_MIGRATED_REVID=116351222
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After completion of the build, there is no need to update the
progress bar any more. Its last line can just move to the scrollback
buffer. The advantage of doing so, is that we then can pass through
STDOUT and STDERR events without additional interference, like line
ending to be sure to know where we position the progress bar and
additional control characters to position the progress bar itself.
In particular, the preformated status report of the tests that were
run will be displayed properly. This makes the experimental UI also
minimally usable for tests.
--
Change-Id: Idaa389b93fc8c9c46c0930f66b4f69b16c3d2e0b
Reviewed-on: https://bazel-review.googlesource.com/#/c/3046
MOS_MIGRATED_REVID=116350626
|
|
|
|
|
|
|
|
|
|
|
|
| |
By not only having a unique identifier for each running action, but
also remembering additional information about the actions, in particular
the action itself, we can provide a more meaningful description of
the currently running actions in the progress bar.
--
Change-Id: I34760a437bf731f057162ca4d08368fe35d4bc71
Reviewed-on: https://bazel-review.googlesource.com/#/c/3045
MOS_MIGRATED_REVID=116349484
|
|
|
|
|
|
|
|
|
|
| |
To improve reporting, in particular about the actions to carry out,
make use of the ExecutionProgressReceiver.
--
Change-Id: I9295199e4c6d9626a193b48b8f332ab2af8e3014
Reviewed-on: https://bazel-review.googlesource.com/#/c/3044
MOS_MIGRATED_REVID=116347930
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116292374
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116272974
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke depot: []
*** Original change description ***
Skylark aspects should always output to bin directory.
--
MOS_MIGRATED_REVID=116264598
|
|
|
|
|
|
|
|
|
|
|
| |
The event raised at this occasion also provides the ExecutionProgressReceiver,
so that any UI subscribing to this event has access to up-to-date progress
information.
--
Change-Id: I366497a61f92dad21de6081e5b4f1ed1e19eda12
Reviewed-on: https://bazel-review.googlesource.com/#/c/3043
MOS_MIGRATED_REVID=116256754
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116255991
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using mandatoryProvidersList to validate python rules' dependency.
Added a SkylarkProvider named 'py' which is a SkylarkClassObject in Java and a
struct in Skylark. Native python rule and Skylark python rule should have this provider
so that they can depend on each other.
RELNOTES[NEW]: Native python rule can depend on skylark rule as long as skylark
rule provides 'py' provider.
--
MOS_MIGRATED_REVID=116241504
|
|
|
|
|
|
|
| |
are created, as opposed to when they are requested from the ParallelEvaluator. That delay can lead to large memory spikes and churn.
--
MOS_MIGRATED_REVID=116224565
|
|
|
|
|
|
|
| |
Fixed bazel github issue #978
--
MOS_MIGRATED_REVID=116164610
|