| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
RELNOTES[NEW]: A new java test runner that support XML output and test filtering is supported.
It can be used by specifying --nolegacy_bazel_java_test or by speicifying the test_class
attribute on a java_test.
--
MOS_MIGRATED_REVID=112028955
|
|
|
|
|
|
|
| |
version.
--
MOS_MIGRATED_REVID=111978539
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=111866202
|
|
|
|
|
|
|
| |
...instead of throwing an uncaught exception and printing a stack trace. Fixes #409.
--
MOS_MIGRATED_REVID=111850179
|
|
|
|
|
|
|
|
|
|
| |
In particular, don't immediately call into the ForTesting functions; I need to
refactor some code that is called from here, and the semantics when called
from ide info should not change. Changes to semantics when called from tests
are much less problematic - we can simply run all the tests.
--
MOS_MIGRATED_REVID=111846384
|
|
|
|
|
|
|
|
|
|
|
| |
Should fix #587.
RELNOTES: Support for downloading remote resources through proxies by setting HTTP_PROXY (or HTTPS_PROXY).
--
Change-Id: I4ae18c4f1a9e911e538efd446323e279e9776eec
Reviewed-on: https://github.com/bazelbuild/bazel/pull/759
MOS_MIGRATED_REVID=111708438
|
|
|
|
|
|
|
| |
For bazel on non-darwin architectures, this will simply be a stub, and should never be invoked. On darwin arcitectures, the tool will map xcode version to xcode path on the host system.
--
MOS_MIGRATED_REVID=111651147
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke build of Bazel tests on ci.bazel.io
See http://ci.bazel.io/job/Bazel/JAVA_VERSION=1.8,PLATFORM_NAME=ubuntu_15.10-x86_64/280/console
Found using git bisect and /tmp/bazel-bin build --nobuild //src/tools/generate_workspace/src/main/java/com/google/devtools/build/workspace:workspace
*** Original change description ***
Factor implementation of bazel-specific cpp logic out of devtools/build/lib/BUILD into subpackage, to allow the objc implementation to extend that logic without a circular dependency. In particular, create a subpackage at lib/bazel/rules, and move relevant targets that were in lib/bazel down to the subpackage.
--
MOS_MIGRATED_REVID=111632586
|
|
|
|
|
|
|
|
|
|
| |
Fixes #733.
RELNOTES: Relative paths can now be used for 'path' with new_local_repository
and local_repository.
--
MOS_MIGRATED_REVID=111620894
|
|
|
|
|
|
|
| |
directory traversal and package loading, and the other which requests deps on all the transitive targets. We need values from the first half, but the second half can fail to evaluate because of a target cycle. By splitting them, we ensure that there will be values in the graph, so we can get the targets below a directory even if there are cycles present.
--
MOS_MIGRATED_REVID=111609889
|
|
|
|
|
|
|
| |
environment variables to pass to actions
--
MOS_MIGRATED_REVID=111608329
|
|
|
|
|
|
|
| |
devtools/build/lib/BUILD into subpackage, to allow the objc implementation to extend that logic without a circular dependency. In particular, create a subpackage at lib/bazel/rules, and move relevant targets that were in lib/bazel down to the subpackage.
--
MOS_MIGRATED_REVID=111602013
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
e.g. a['key'] = value
is handled through a proper lvalue, instead of using syntactic sugar.
Benefits include:
- better error messages (reference to the '+' operator was cryptic)
- more robust, e.g. it is compatible with the += operator
- can be used in a tuple, e.g. a[1], a[2] = 3, 4
- it is a step towards mutable dict
--
MOS_MIGRATED_REVID=111597545
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=111537858
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=111453115
|
|
|
|
|
|
|
| |
CppSemantics instead.
--
MOS_MIGRATED_REVID=111406721
|
|
|
|
|
|
|
|
|
| |
cause of a catastrophic failure (this is distinct from a crash).
Also clean up catastrophe logic in ParallelEvaluator -- the catastrophic nature of an exception is important only if the build is keep_going, and only if the exception is catastrophic can we have an exception in the first place.
--
MOS_MIGRATED_REVID=111293164
|
|
|
|
|
|
|
|
|
| |
This commit adds proto messages that represent configurable values,
and modifies attribute value serialization code to handle those
values, which are called SelectorLists.
--
MOS_MIGRATED_REVID=111149272
|
|
|
|
|
|
|
| |
for use in tools.
--
MOS_MIGRATED_REVID=111142252
|
|
|
|
|
|
|
| |
import as a PathFragment.
--
MOS_MIGRATED_REVID=111138001
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110840166
|
|
|
|
|
|
|
| |
Add some functions to Build, allow method calls.
--
MOS_MIGRATED_REVID=110835163
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
files in external repositories.
In addition:
- Cleaned up and refactored some tests to reflect the new loading behavior.
Deferred to future CLs:
- Updating Bazel Skylark documentation to reflect the new load form.
- Enabling command-line loading of Aspects via labels.
RELNOTES: Skylark load statements may now reference .bzl files via build labels, in addition to paths. In particular, such labels can be used to reference Skylark files in external repositories; e.g., load("@my_external_repo//some_pkg:some_file.bzl", ...). Path-based loads are now deprecated and may be disabled in the future. Caveats: Skylark files currently do not respect package visibility; i.e., all Skylark files are effectively public. Also, loads may not reference the special //external package.
--
MOS_MIGRATED_REVID=110786452
|
|
|
|
|
|
|
| |
Fixes #587.
--
MOS_MIGRATED_REVID=110785300
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110778743
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110746503
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110672372
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110670806
|
|
|
|
|
|
|
|
|
|
| |
I had to make a small change to ExternalFilesHelper. The Bazel test setup
creates a remote repository for the tools, so we always have external files,
incl. during loading. However, some of the tests don't setup an output
directory, but instead pass null, which would lead to a crash.
--
MOS_MIGRATED_REVID=110669993
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110446625
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
The original CL broke our CI because Bazel used an old version of Guava (18.0 instead of 19.0). We fixed this problem, so we can roll forward the original change.
*** Original change description ***
Automated [] rollback of [].
*** Reason for rollback ***
Broke the build: http://ci.bazel.io/job/Bazel/262/
*** Original change description ***
Skylark: implemented more string functions (isalnum, isdigit, etc).
--
MOS_MIGRATED_REVID=110439750
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke the build: http://ci.bazel.io/job/Bazel/262/
*** Original change description ***
Skylark: implemented more string functions (isalnum, isdigit, etc).
--
MOS_MIGRATED_REVID=110383960
|
|
|
|
|
|
|
|
|
| |
will make it easier to manage the transition from legacy Skylark path-style loads to label-based loads. We handle both old-style (path-based) imports and new-style (label-based) imports.
This class is in the cmdline package since it depends on Label-related code in the same package. The cmdline package depends on the syntax package, so this class can't go there, which would otherwise be a reasonable place to put it.
--
MOS_MIGRATED_REVID=110372547
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110361527
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Skylark into their own package. This allows, e.g., classes in the syntax package to access classes in the cmdline package without creating circular dependencies.
While we're here:
- Removed a couple of unused BUILD deps flagged in [].
- Updated SkylarkRuleImplementationFunctionsTest to remove non-ASCII characters and
clarify the intent of the test.
--
MOS_MIGRATED_REVID=110360763
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110356954
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110356439
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks ci.bazel.io: http://ci.bazel.io/job/Bazel/JAVA_VERSION=1.7,PLATFORM_NAME=darwin-x86_64/256/console
*** Original change description ***
Open source PackageCacheTest.
--
MOS_MIGRATED_REVID=110352000
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110348607
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
external/ directory, i.e. were created by Bazel.
This avoids a cycle that arose when a file is load()ed from the WORKSPACE file that is reached through a symlink to an external directory:
* The WORKSPACE file depends on the package lookup node of the .bzl file
* The package lookup node (transitively) depends on wherever the symlink points
* The target of the symlink is an external file and as such, it depends on the WORKSPACE file
This will probably be, erm, interesting to solve when we get as far as to load stuff from external repositories in the WORKSPACE file, but we are just not there yet.
--
MOS_MIGRATED_REVID=110344658
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110321278
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110261986
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110155243
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110153755
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110153136
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110151036
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110150657
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110141376
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
directory that I should populate". The directory itself is not created because local_repository actually puts a symlink in its place.
As a side effect, make HTTP downloading, git cloning and archive decompressing not be SkyFunctions. This is necessary because it needs to be the RepositoryFunction and not a
dependent SkyFunction that populates the output directory, because it that's the case what happens is:
1. RepositoryDelegatorFunction cleans up the directory and prepares it for RepositoryFunction
2. RepositoryFunction calls env.getValue(<function that populates the directory>)
3. That value hasn't been computed yet, thus RepositoryDelegatorFunction returns early
4. The function that populates the directory is called
5. RepositoryDelegatorFunction is restarted
6. RepositoryDelegatorFunction cleans up the directory
7. RepositoryFunction calls env.getValue(), and nothing is done because the value has already been computed
8. RepositoryDelegatorFunction proudly returns, even though the directory is actually empty
Another way to solve this problem would be to make RepositoryFunction not clean the directory up on Skyframe restarts, but that means that we'd need to keep state somewhere, which doesn't strike me as a particularly great idea because let's keep state outside of Skyframe only when absolutely necessary (e.g. the marker files for cross-server instance persistence of downloaded repositories). That "somewhere" could either be a member variable of RepositoryDelegatorFunction or the file system.
Note that this change causes external communication to be re-done in a few more cases than before (see that changes to the test cases), but I'd rather we be correct and simple than fast. We can optimize things later if needed and there is enough complexity going around, thank you very much.
--
MOS_MIGRATED_REVID=110134397
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110025690
|