| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
See Issue #2120: if we specify /MD for copts, we should attempt to use
MSVCRTx.lib instead of LIBCMTx.lib.
Closes #2862.
PiperOrigin-RevId: 154032031
|
|
|
|
| |
PiperOrigin-RevId: 154017157
|
|
|
|
|
|
|
|
|
| |
the host.
Also add a single instance of that platform for standard usage.
Change-Id: I0e7a8eb3a44099076540c8d955fc0c0c70447583
PiperOrigin-RevId: 153878880
|
|
|
|
|
| |
Change-Id: Ib2bbd1b35985c4ec2d1e411aea4b32af7433a426
PiperOrigin-RevId: 153856560
|
|
|
|
|
|
|
|
|
|
| |
* Make quit & reload actually kill the server, to prevent bind errors.
* Added an arg to bind to $HOSTNAME, instead of just localhost, for
ease of code review.
* Makes option parsing a little more robust.
* Moves "build the jekyll tree" out of the "serve forever" loop.
PiperOrigin-RevId: 153840306
|
|
|
|
| |
PiperOrigin-RevId: 153831526
|
|
|
|
|
|
|
|
|
|
| |
For the TargetComplete event (not for the completion of aspects) readd
the reporting of outputs, but only for the default output group. This
will help existing applications to still report the outputs of a target,
till they transferred to handling named sets of files.
Change-Id: I1b0730b38bdc18f8fb2ccf859a7fee8f1b7f0cac
PiperOrigin-RevId: 153828334
|
|
|
|
|
|
|
|
|
|
|
| |
selected even if they're not the preferred one on a platform.
Simplify the SandboxActionContextProvider and remove the warning about
sandboxing being unsupported. With the ProcessWrapperSandboxedStrategy
now being reliable enough and the strategies printing their real name in
the UI, this is overall a better UX.
PiperOrigin-RevId: 153825986
|
|
|
|
|
|
| |
With the process-wrapper improvements and the additional deletion of the sandbox base in the SandboxModule in, this should be reliable enough. The warning was also not actionable for users and annoyed them, so let's get rid of it.
PiperOrigin-RevId: 153823045
|
|
|
|
|
|
|
|
| |
This uses Linux's PR_SET_CHILD_SUBREAPER and FreeBSD's PROC_REAP_ACQUIRE features to become an init-like process for all (grand)children spawned by process-wrapper, which allows us to a) kill them reliably and then b) wait for them reliably. Before this change, we only killed the main child, waited for it, then fired off a kill -9 on the process group, without waiting for it. This led to a race condition where Bazel would try to use or delete files that were still helt open by children of the main child and thus to bugs like #2371.
This means we now have reliable process management on Linux, FreeBSD and Windows. Unfortunately I couldn't find any feature like this on macOS, so this is the only OS that will still have this race condition.
PiperOrigin-RevId: 153817210
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 153807467
|
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/issues/2848 was fixed by de48d7d.
RELNOTES: None
PiperOrigin-RevId: 153805058
|
|
|
|
| |
PiperOrigin-RevId: 153787279
|
|
|
|
|
|
|
|
|
| |
The consumers of ":lipo_context_collector" only do anything with it in
optimization builds.
Also remove an outdated comment in FdoSupport.
PiperOrigin-RevId: 153748937
|
|
|
|
|
|
| |
The Java project used in the tutorial has stayed the same.
PiperOrigin-RevId: 153747213
|
|
|
|
|
|
|
| |
Without this, serve-docs.sh prints:
Deprecation: You appear to have pagination turned on, but you haven't included the `jekyll-paginate` gem. Ensure you have `gems: [jekyll-paginate]` in your configuration file.
PiperOrigin-RevId: 153737266
|
|
|
|
|
|
|
|
|
|
|
| |
Because SkylarkClassObject declares equals, hashCode, and toString,
AutoValue doesn't bother creating those, but since these classes didn't
pass any data back to SkylarkClassObject, the defined methods don't work
properly. This shows up as all instances of a class having the same
hashCode and being equals() to each other.
Change-Id: I50734f04369231cd2141dd368b04a3f0997a7d18
PiperOrigin-RevId: 153735995
|
|
|
|
|
|
| |
RELNOTES: n/a
PiperOrigin-RevId: 153735445
|
|
|
|
|
|
| |
Fixes #2853.
PiperOrigin-RevId: 153730500
|
|
|
|
|
|
| |
It's failing with sandboxing.
PiperOrigin-RevId: 153720082
|
|
|
|
|
| |
Change-Id: Ic8c57c0ce78b5875135d5d1f19629ee40fd8f5f2
PiperOrigin-RevId: 153718869
|
|
|
|
|
|
|
|
| |
- Make the default Bazel release artifacts include the bundled JDK.
- Create additional Bazel release artifacts without a bundled JDK.
Change-Id: If87c986507ae8e7dbbf0e8f163dd0073a206b265
PiperOrigin-RevId: 153718827
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 153716003
|
|
|
|
|
|
|
|
| |
Fixes #616.
Closes #2807.
PiperOrigin-RevId: 153714590
|
|
|
|
|
|
| |
This feature is unused and depends on emma, which is obsolete.
PiperOrigin-RevId: 153713051
|
|
|
|
|
|
|
|
|
| |
the bug that the RemoteWorker would fail to upload outputs that were too big to send in a single gRPC message.
Fixes #2822.
RELNOTES: n/a
PiperOrigin-RevId: 153710733
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before, we correctly replaced CppConfiguration with HipCppConfiguration for hip
builds, but we didn't update FeatureConfiguration. As Blaze was not using
action_configs for compile actions, compiler tool was taken from configuration
at the action creation time, not from FeatureConfiguration, so the tool was
correct. Command line flags (some of them) were computed by
FeatureConfiguration, but luckily the toolchains were so similar that it
worked.
In https://github.com/bazelbuild/bazel/commit/e1d692e486a2f838c3c894fd9de693fabd6685ed I tried to use action_configs for compile actions. The result
was that compiler tool was taken from configuration at the CppConfiguration
creation time, that was put into FeatureConfiguration, and that was used in
action creation time. Sadly, the tool in CppConfiguration was different that
the tool in HipCppConfiguration, and b/37315875 was discovered.
This cl also uppdates FeatureConfiguration when HipCppConfiguration is
replaced.
RELNOTES: None.
PiperOrigin-RevId: 153710405
|
|
|
|
|
|
|
| |
Part of #2841.
Change-Id: I4d1e63aac6b5ed6beb9854b9b67d2899d8da4418
PiperOrigin-RevId: 153705466
|
|
|
|
|
|
| |
This is the first part of a two-step migration to the new versions.
Change-Id: I3835b3db386f43cd00ca0d68c7fd2a42c3f9714f
|
|
|
|
|
|
|
|
|
|
| |
This module rely on an un-maintained codepath and is hardly used by anyone.
We should also archive the code from dash until we can revive it with BEP
RELNOTES[INC]: --use_dash, --dash_url and --dash_secret are removed.
PiperOrigin-RevId: 153701824
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We need to lookup repositories as part of converting exec paths to artifacts,
which in turn is needed for action cache lookups. These lookups should not
cause a Skyframe exit, so we must not throw an exception here, unless the
error makes it impossible to continue. Instead, we need to leave the decision
whether to error out or not to the caller.
Note that we may unnecessarily fetch a remote repository in order to do the
action cache lookup, even if the action no longer depends on the input file,
although this should only be possible for C++ compile actions. It's possible
that there's another bug in the C++ compile action key computation that also
contributes.
This change also makes it so that the post-resolution action cache code
ignores any errors wrt. repository lookup rather than throwing. If any of the
paths could not be found, then the action cache lookup fails and we re-execute
the corresponding action, which is exactly what should happen.
Fixes #2759.
PiperOrigin-RevId: 153696243
|
|
|
|
|
|
|
| |
Fixes #2848.
RELNOTES: None.
PiperOrigin-RevId: 153692641
|
|
|
|
|
|
|
| |
list of built-in include directories available to Skylark through it.
RELNOTES: None.
PiperOrigin-RevId: 153684976
|
|
|
|
|
|
| |
Fixes #1413.
PiperOrigin-RevId: 153684106
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
The depot has been fixed: unknown commit
*** Original change description ***
Partial rollback of unknown commit
PiperOrigin-RevId: 153646328
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Causes issues with library R generation.
*** Original change description ***
Refactor the RClassGenerator to be reusable for different packages.
RELNOTES: None
PiperOrigin-RevId: 153641485
|
|
|
|
|
|
|
|
| |
The jar will be added in
https://bazel-review.googlesource.com/c/10050/
Change-Id: I6e8228f8dbc627cd22bab45ae8eda5b4f332cbda
PiperOrigin-RevId: 153634892
|
|
|
|
|
|
| |
RELNOTES: fix idempotency issue with desugaring lambdas in interface initializers for android
PiperOrigin-RevId: 153634357
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 153619067
|
|
|
|
|
|
|
|
| |
Add a dynamic equivalent for LIPO_COLLECTOR transition.
Rename LipoDataTransition (which handles DATA transition) to DisableLipoTransition. A future change will add a corresponding EnableLipoTransition (which will model TARGET_CONFIG_FOR_LIPO).
PiperOrigin-RevId: 153611898
|
|
|
|
| |
PiperOrigin-RevId: 153610163
|
|
|
|
|
|
|
| |
Added toMap()/fromMap() to OptionsParser, and moved the implementation of OptionsBase#asMap away from OptionsParserImpl.
RELNOTES: None
PiperOrigin-RevId: 153602479
|
|
|
|
|
|
| |
TESTED: local server
RELNOTES: n/a
PiperOrigin-RevId: 153599636
|
|
|
|
|
|
|
|
|
|
|
| |
RELNOTES: Adds a --override_repository option that takes a repository
name and path. This forces Bazel to use the directory at that path
for the repository. Example usage:
`--override_repository=foo=/home/user/gitroot/foo`.
Fixes #1266
PiperOrigin-RevId: 153599291
|
|
|
|
| |
PiperOrigin-RevId: 153589856
|
|
|
|
|
| |
WANT_LGTM=all
PiperOrigin-RevId: 153584480
|
|
|
|
| |
PiperOrigin-RevId: 153584278
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is to minimize the likelihood of obscure policy conflict. Now, the last policy on
a flag (after policy expansion) will be the only one in the "canonical" invocation
policy. There should be no reason for explicitly setting multiple policies on a single
flag, but if an expansion flag is policy'd and one of its children has a more specific
policy on it, make sure that the policy on the child flag is after the policy on the
expansion flag.
Note that this restriction (only the last policy gets applied) also applies for repeatable flags. Make sure all values being set to a repeatable flag are set in a single SetValue operation, with multiple flagValues set.
PiperOrigin-RevId: 153584034
|
|
|
|
|
|
|
|
|
| |
Without this change, //src/test/shell/bazel:bazel_toolchain_test is failing
when remote caching is enabled.
Workaround for #2845.
PiperOrigin-RevId: 153574893
|
|
|
|
|
|
|
|
| |
eventually be able to fix Android builds.
Progress on #2848.
Change-Id: I3b96425c2f5a4708629882e730d4907abd1226a6
|