| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
When using LLVM LIPO is automatically mapped to ThinLTO.
While for LIPO, fully dynamic linking needs to be off for correctness issues,
there is no such restriction for ThinLTO.
RELNOTES[NEW]: Do not disable fully dynamic linking with ThinLTO when invoked via LIPO options.
PiperOrigin-RevId: 162918429
|
|
|
|
|
|
|
| |
Also change it to java.time.Duration, rather than Jodatime. Now that we're on
Java 8, we no longer need Jodatime.
PiperOrigin-RevId: 162917526
|
|
|
|
|
|
|
| |
It's bad to crash with an exception, let's show proper rule error instead.
RELNOTES: None.
PiperOrigin-RevId: 162916138
|
|
|
|
| |
PiperOrigin-RevId: 162915070
|
|
|
|
|
| |
RELNOTES:
PiperOrigin-RevId: 162914414
|
|
|
|
|
|
|
|
| |
After the ByteUploader changes, the Retrier no longer needs the onFailure(s) functions. Removing them will simplify both the code and the stack traces used for debugging problems.
TESTED=unit tests
RELNOTES: none
PiperOrigin-RevId: 162913762
|
|
|
|
|
|
|
| |
Fixes #3183.
Change-Id: Id208e0b723f0ffe8313cae4852dd77df43be477f
PiperOrigin-RevId: 162911817
|
|
|
|
|
|
|
|
|
| |
In this way, for each event there can only be two event payloads
for every event identifier: the expected one, and the Aborted event.
The type of failure will be reported in the AbortReason enum value.
Change-Id: Icce225ec156d1fc20c8facd18df13343712f775c
PiperOrigin-RevId: 162911732
|
|
|
|
|
|
| |
This removes a bunch of code duplication that I previously introduced.
PiperOrigin-RevId: 162909430
|
|
|
|
|
|
|
| |
Fixes #2931.
RELNOTES: None.
PiperOrigin-RevId: 162907348
|
| |
|
|
|
|
| |
PiperOrigin-RevId: 162906926
|
|
|
|
| |
PiperOrigin-RevId: 162906919
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 162906513
|
|
|
|
|
|
|
|
|
|
| |
We don't yet have a SKIPPED test status. So for now we report
"NO STATUS".
Also moved top-level constraint checking to its own file,
since its logic is getting more complicated.
PiperOrigin-RevId: 162790879
|
|
|
|
| |
PiperOrigin-RevId: 162788157
|
| |
|
|
|
|
|
|
| |
overwritten, losing info (http://ci.bazel.io/job/bazel-tests/899/BAZEL_VERSION=latest,PLATFORM_NAME=ubuntu_16.04-x86_64/consoleFull).
PiperOrigin-RevId: 162764897
|
|
|
|
|
|
|
| |
as printing the merge error report. The stack traces duplicated the error report and gave the impression that the error may be an internal error instead of a build error.
RELNOTES: None.
PiperOrigin-RevId: 162755827
|
|
|
|
| |
PiperOrigin-RevId: 162755817
|
|
|
|
|
|
|
|
|
|
| |
an iterable of events without calling into the heavyweight MoreAsserts.
Use that in Skyframe instead of MoreAsserts.
Also delete an unused method in MoreAsserts.
PiperOrigin-RevId: 162754283
|
|
|
|
|
|
| |
Fixes #3423
PiperOrigin-RevId: 162754159
|
|
|
|
| |
PiperOrigin-RevId: 162742684
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 162738376
|
|
|
|
|
|
|
| |
Fixes #2987.
Change-Id: I359a74b37a670e3953cc737a416c0e9573e547f0
PiperOrigin-RevId: 162738265
|
|
|
|
|
|
|
|
| |
The native launcher is implemented based on this design doc:
https://docs.google.com/document/d/1z6Xv95CJYNYNYylcRklA6xBeesNLc54dqXfri0z0e14/edit?usp=sharing
Change-Id: I83bae844f792a587ce0e342a3c0f238b760afeaa
PiperOrigin-RevId: 162736269
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 162736242
|
|
|
|
|
|
|
| |
Intended to be an introduction before talking about macros.
RELNOTES: None.
PiperOrigin-RevId: 162733299
|
|
|
|
|
|
|
| |
This is the first CL to remove MSYS Bazel.
RELNOTES:
PiperOrigin-RevId: 162731750
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rollforward with fix
*** Original change description ***
Automated rollback of commit e5f970906594d9097bb7c3736b2de1750cc8655f.
*** Reason for rollback ***
Break apple test on darwin.
*** Original change description ***
Refactor docker tests to be buildable without docker.
This make this build a bit non-deterministic since the way
it will be built depend on wether docker is installed or not.
We now use the docker_pull from bazelbuild/continuous-integration
to generate the base docker images and generate a fake docker binary
that j...
***
PiperOrigin-RevId: 162731090
|
|
|
|
|
|
|
| |
This is more consistent with other values, and removes the need to inject it
into the constructor of the various strategy implementations.
PiperOrigin-RevId: 162729187
|
|
|
|
|
|
|
|
|
|
|
| |
Replace blaze_util::AsWindowsPathWithUncPrefix
with AsAbsoluteWindowsPath, which always returns
an absolute path.
Fixes https://github.com/bazelbuild/bazel/issues/2935
RELNOTES: none
PiperOrigin-RevId: 162727218
|
|
|
|
|
|
|
| |
Fixes #2874.
Change-Id: I636e0f6b56a1e33adfc64e90f36f76d4254d0281
PiperOrigin-RevId: 162726099
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 162725697
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The current working directory may not be longer
than MAX_PATH, otherwise SetCurrentDirectoryW
fails.
It may, but should not contain a "\\?\" prefix,
otherwise the Java code won't be able to parse it.
Therefore convert the path to a 8dot3 style path
in blaze_util::ChangeDirectory and use
SetCurrentDirectoryA.
RELNOTES: none
PiperOrigin-RevId: 162720636
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In this change:
- add support for absolute-on-current-drive paths
(e.g. "\foo", meaning "c:\foo")
- report error for relative-on-current-drive paths
(e.g. "c:" and "c:foo")
- report error for remote Windows paths
(e.g. "\\servername\path\on\server")
- update blaze_util::AsWindowsPath comments
- update tests
RELNOTES: none
PiperOrigin-RevId: 162719763
|
|
|
|
| |
PiperOrigin-RevId: 162715709
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 162715619
|
|
|
|
|
|
|
|
| |
As the ordering in which features are defined matters, let's move all the
crosstool patching logic to a single place in CppActionConfigs.
RELNOTES: None.
PiperOrigin-RevId: 162712170
|
|
|
|
| |
PiperOrigin-RevId: 162676133
|
|
|
|
|
| |
Change-Id: I76d785dbbcd2c5cf30ab5d130e82b2819931651a
PiperOrigin-RevId: 162672358
|
|
|
|
|
|
|
| |
Fixes #3354.
Change-Id: I1525b5fc6e44cce335744b1d5883be71812003ed
PiperOrigin-RevId: 162672218
|
|
|
|
|
|
|
| |
This has the added benefit of improving ObjcProvider documentation generated in bazel docs.
RELNOTES: None.
PiperOrigin-RevId: 162658384
|
|
|
|
|
|
| |
The plan is to add it to ActionExecutionContext, which is also there.
PiperOrigin-RevId: 162656835
|
|
|
|
|
|
|
| |
We previously only add those under genfiles root. But J2ObjC and objc proto headers are under the bin root, which we may also fix in the near future.
RELNOTES: None.
PiperOrigin-RevId: 162656166
|
|
|
|
| |
PiperOrigin-RevId: 162655959
|
|
|
|
|
|
|
|
|
| |
success.
This can happen per spec, if multiple builds try to upload the same blob concurrently.
Also, added this to the RemoteWorker, per spec.
PiperOrigin-RevId: 162647548
|
|
|
|
|
|
|
|
| |
This flag has been a no-op for a while with a deprecation warning that it will
be removed.
RELNOTES: Remove --experimental_android_use_singlejar_for_multidex.
PiperOrigin-RevId: 162643922
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rolling this back as it was the example BUILD file that was incorrect, not the tutorial itself. Submitted an updated BUILD file in commit 6abf4b9.
*** Original change description ***
the build file and bash example out of synch
comparing to the latest code in the java tutorial repo
Closes #3419.
PiperOrigin-RevId: 162635241
|
|
|
|
|
|
|
| |
Part of #2219.
Change-Id: Id4929d5ddcd57b4635af5e513eb9a09f16a78e71
PiperOrigin-RevId: 162634398
|