| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
RELNOTES: The --[no]experimental_disable_jvm command line option is not
supported anymore.
PiperOrigin-RevId: 181575259
|
|
|
|
|
|
|
|
|
|
| |
For different applications, different size of buffered stdout/stderr might be
acceptable; essentially it is a trade off between latency and number of messages
generated. Put this trade off into the control of the user by adding an appropriate
flag.
Change-Id: I8fb4d19a336205fa28d01340f2f0b2be9b4a24f3
PiperOrigin-RevId: 181570242
|
|
|
|
|
|
|
|
|
|
|
| |
to get the remote execution properties.
Fixes #4128.
This reverts commit 3ce42ef3074ee6d3ac7d9968381c8c0a51d9d38d.
Change-Id: I8b9ad5099f6334c2488a22baf05d0b273e10f776
PiperOrigin-RevId: 181550828
|
|
|
|
| |
PiperOrigin-RevId: 181545835
|
|
|
|
| |
PiperOrigin-RevId: 181533491
|
|
|
|
|
|
| |
superclass of the class in question.
PiperOrigin-RevId: 181524469
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 181523499
|
|
|
|
|
|
| |
This should fix the bazel-slow-tests job on CI. :)
PiperOrigin-RevId: 181510264
|
|
|
|
|
|
| |
and #toValue. I saw significant contention from this method in some experiments, and the synchronization isn't needed, since we only call these methods on done nodes (as determined by #isDone), and a node that is observably done cannot racily change its value.
PiperOrigin-RevId: 181507133
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 181506851
|
|
|
|
|
|
|
| |
attribute is on.
RELNOTES: none
PiperOrigin-RevId: 181503682
|
|
|
|
|
|
| |
See #4422
PiperOrigin-RevId: 181497117
|
|
|
|
| |
PiperOrigin-RevId: 181491528
|
|
|
|
|
|
|
|
| |
This is a rollforward -- the previous attempt was rolled back due to incorrectly adding test sources.
In addition, the newly checked in tests do not work on Windows, and are thus disabled on the Windows platform. I suspect this is due to a bug in the compile-testing library.
RELNOTES: None.
PiperOrigin-RevId: 181482589
|
|
|
|
| |
PiperOrigin-RevId: 181482268
|
|
|
|
|
|
|
|
|
| |
- Reorder Info methods for consistency with ClassObject
- "StructConstructor" -> "StructProvider"
- Added javadoc
RELNOTES: None
PiperOrigin-RevId: 181469643
|
|
|
|
|
|
|
| |
Fixes #4414
Change-Id: I06eac192b5be84bd84190980fbcd05574e3a4439
PiperOrigin-RevId: 181465165
|
|
|
|
|
|
|
|
| |
attribute.
This fixes an issue where CC_FLAGS was being overwritten.
PiperOrigin-RevId: 181463694
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 181462949
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks nightly: b/71790513
*** Original change description ***
C++ refactoring: Separate compilation and linking calls to CcLibraryHelper
RELNOTES:none
PiperOrigin-RevId: 181457811
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rolling back due to previous CL breaking nightly.
*** Original change description ***
Removes call to CcLibraryHelper.link() in cc_binary.
This call is unnecessary when the sources of the cc_binary are being built as
EXECUTABLE or DYNAMIC LIBRARY. The call doesn't do anything, no linking outputs
are returned.
RELNOTES:none
PiperOrigin-RevId: 181457495
|
|
|
|
|
|
|
|
|
| |
This call is unnecessary when the sources of the cc_binary are being built as
EXECUTABLE or DYNAMIC LIBRARY. The call doesn't do anything, no linking outputs
are returned.
RELNOTES:none
PiperOrigin-RevId: 181455622
|
|
|
|
|
|
|
|
| |
It contained no fields or any other information accessible from Skylark, so it's not a big loss.
RELNOTES[INC]: ctx.fragments.jvm is not available anymore.
PiperOrigin-RevId: 181455474
|
|
|
|
|
|
|
|
|
|
| |
JavaCompilationArgsProvider.
Added tests for checking JavaCompilationArgsProvider state.
All other providers will be implemented in next CLs.
RELNOTES:none
PiperOrigin-RevId: 181451235
|
|
|
|
|
|
|
|
|
|
| |
A build might fail because of a visibility violation that does
not happen at a top-level target. To avoid confusion, add a separate
namespace for configured targets that are just mentioned to report
the details of an error.
Change-Id: I86587f7489500f1d888bae6ce3d6f4bd79ea1609
PiperOrigin-RevId: 181448003
|
|
|
|
|
|
|
| |
* Creates an enum for cpu transformer, which is easier to serialize than an opaque function. This also means moving FakeCPU to avoid introducing a circular dependency.
* Adds a CODEC to Path using InjectingObjectCodec.
PiperOrigin-RevId: 181445911
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This should not cause a user-visible change: --{host_,}javabase was already
required to point to a java_runtime_suite / java_runtime rule, the only change is that
we now enforce it differently.
If anything, this makes Bazel more lenient in that it now accepts Skylark rules
that provide JavaRuntimeInfo, but I doubt anyone does that, since it does not
work at HEAD.
RELNOTES: None.
PiperOrigin-RevId: 181444563
|
|
|
|
|
|
|
|
| |
After some consideration, I think it makes sense to always allow a getDigest call, instead of specifying it as disallowed based on type. This is a follow-up CL for a previous CL introducing the getType method, which increased the complexity of the specification.
I have a follow-up CL, which is related, namely unknown commit. After that CL, Metadata instances for directories (but not Filesets) also have digests rather than using mtime, which is compatible with the documentation changes made here. Said CL is solving a correctness issue with directory dependencies, which I think we want, and using the digest in the Metadata is a natural way to get correct action cache lookups.
PiperOrigin-RevId: 181440548
|
|
|
|
|
|
|
|
|
|
|
|
| |
Continuation of https://github.com/bazelbuild/bazel/pull/4356
An approach at supporting strip_prefix with the git skylark rules.
This approach unfortunately uses symlinks since you cannot clone a subset of a git repository. It creates a tmp directory which is the 'real' clone and then provides a link in place of the expected location of the repository to the path of the required prefix. Behaviour is only changed if a strip_prefix is provided.
Closes #4368.
PiperOrigin-RevId: 181438640
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 181397098
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rolling forward after underlying issue has been fixed.
*** Original change description ***
Automated rollback of commit d50cbbeef115f28c0cea1ac17572e0f12c0cf312.
*** Reason for rollback ***
b/71442447
*** Original change description ***
Remove synchronization from file system.
After the path refactor we will no longer have path instances to synchronize on.
The underlying OS file systems are already naturally thread safe, that is, their internal data structures cannot be damaged. Any further synchronization (eg. races between directory creation and deletion) has to be managed at the client level.
The l...
***
PiperOrigin-RevId: 181368707
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rolling forward after the underlying issue has been fixed.
*** Original change description ***
Automated rollback of commit 6a54339bb943702bd7dffc43f85267dac98dc355.
*** Reason for rollback ***
b/71442447
*** Original change description ***
Call through to Path#createDirectoryAndParents from FileUtils.
This CL removes a method that due to its implementation causes threading difficulties for Path#createDirectory.
The tests for the method are brought across to FileSystemTests since the methods are now implemented natively by the FileSystem classes. The tests were also cleaned up.
The test revealed an edge c...
***
PiperOrigin-RevId: 181367850
|
|
|
|
|
|
| |
It's otherwise possible that we do other syscalls in between the original syscall and us reading the errno for use in the exception.
PiperOrigin-RevId: 181367811
|
|
|
|
|
|
|
|
|
|
|
|
| |
Both members of Label (String & PackageIdentifier) have memoized hash codes so
this should be marginally more expensive but probably not noticably so. The
benefit is it makes Label objects smaller in certain vm conditions.
As to why things were the way they were, I believe this is from before
PackageIdentifier memoized its hashCode.
RELNOTES: None
PiperOrigin-RevId: 181362077
|
|
|
|
|
|
|
|
| |
We use errno to signal an error in the stat call that gets passed back to Java land. However, between the time we make the failed stat syscall and the time that we read the final value of errno we will very rarely make other syscalls in between, which will stomp the value of errno back to 0. This will get interpreted as "no error, the file exists" by the VFS.
This bug has existed since 2009. Only a perturbation of the sequence of syscalls we make during startup has since caused the bug to surface.
PiperOrigin-RevId: 181358035
|
|
|
|
|
|
|
| |
This has the effect of documenting exposed struct fields on the provider.
RELNOTES: None.
PiperOrigin-RevId: 181346052
|
|
|
|
| |
PiperOrigin-RevId: 181330907
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When Bazel creates the sandbox, it will allow
making non-existent paths writable, as long as the
path is under the sandbox root.
As Bazel adds entries to the sandbox's set of
writable paths, Bazel needs to make sure that it's
not adding symlinks, because doing so would make
the symlink writable, not what the link points to.
If the path is under the sandbox root, then at the
time of setting up the sandbox's writable paths
the path surely doesn't exist yet, but that's OK,
because at that time Bazel didn't yet create the
sandbox root.
If the path is not under the sandbox root, then
Bazel needs to resolve all symlinks on this path,
which is only possible if the path exists,
therefore Bazel checks for the path's existence.
Change-Id: Ic7d99a81905e7401455286c0b375d69b85ece1d5
PiperOrigin-RevId: 181325749
|
|
|
|
|
|
|
|
|
| |
ExecuteDaemon() always returns a defined value.
Fixes #4394.
RELNOTES: None.
PiperOrigin-RevId: 181315375
|
|
|
|
|
|
|
|
|
|
|
| |
The precondition check in line 1274 makes sure that it has Staticness.STATIC.
EXECUTABLE has Staticness.DYNAMIC which precludes the checks from ever being
executed.
NO_SQ=Kokoro failing without giving an actual error.
RELNOTES:none
PiperOrigin-RevId: 181314900
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 181297029
|
|
|
|
| |
Change-Id: I94cdf0ea3e219887515ee52a86bd6d5d65681c67
|
|
|
|
|
|
|
|
| |
These tests don't require a full Skyframe instance, so we might as well move
them to a lighter-weight test class. Also, it turns out that we have duplicate
tests for equality and hashing - this is now explicit.
PiperOrigin-RevId: 181285144
|
|
|
|
| |
PiperOrigin-RevId: 181255541
|
|
|
|
|
|
|
| |
folders for aapt2.
RELNOTES: none
PiperOrigin-RevId: 181226483
|
|
|
|
|
|
|
|
| |
This API mimics the linking logic of apple_binary, and is a step to migrating apple_binary to skylark.
This API is *highly experimental* and subject to change.
RELNOTES: None.
PiperOrigin-RevId: 181215275
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is to fix building android outside of the bazel repository.
To reproduce the issue (on a Windows machine, of course):
1. Copy the examples/android folder from a bazel checkout to a new folder (keep the same folder structure - i.e. `<new folder>/examples/android`)
2. Create a `WORKSPACE` file in `<new folder>` with the `android_sdk_repository` and `android_ndk_repository` rules as described in the example README.
3. `bazel build examples/android/java/bazel:hello_world`
4. Observe the failure to locate `windows_jni.dll`
Closes #4392.
PiperOrigin-RevId: 181181641
|
|
|
|
| |
PiperOrigin-RevId: 181180652
|
|
|
|
|
|
|
|
| |
This simplifies some spawn runners, which no longer have to specially handle
null; unfortunately, the sandbox runners do not support VirtualActionInput,
so they still have to special-case it.
PiperOrigin-RevId: 181175408
|
|
|
|
|
| |
RELNOTES:none
PiperOrigin-RevId: 181169134
|