| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In preparation for allowing aspects to have their own configuration fragments
specified, allow ConfigurationFragmentPolicy.Builder to merge with built policies
more easily, setting up SetMultimaps in place of maps of sets. This changes how
named (Skylark) fragments are declared in the RuleContext builder, hopefully to
be a bit easier to write.
In order to do this, make SkylarkModuleNameResolver the only name resolver in use
(because it is the only name resolver which exists) so as to not worry about
collisions of different name resolvers.
This also changes isLegalConfigurationFragment's one-argument form to mean
"legal in ANY configuration" rather than "legal in the target (NONE)
configuration", as that is how it's used by TransitiveTargetFunction. Uses of it to
mean the latter have been revised to be more explicit.
Also in this CL:
* refactor ConfigurationFragmentPolicy to enforce its contracts about which
ConfigurationTransitions are legal
* use containsEntry or containsValue rather than looking in get(key) or values()
for the configuration fragment multimaps
* add tests for ConfigurationFragmentPolicy
* make SkylarkModuleNameResolver a static method
--
MOS_MIGRATED_REVID=112191439
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, for some types of errors, you'd just see "WORKSPACE file
could not be parsed" if there was a syntax error (instead of what the
syntax error was).
Change-Id: Ia278cf23b79f8daba02917cdfb4cc515a87080b1
--
Change-Id: Ia278cf23b79f8daba02917cdfb4cc515a87080b1
Reviewed-on: https://github.com/bazelbuild/bazel/pull/774
MOS_MIGRATED_REVID=112190322
|
|
|
|
|
|
|
|
|
| |
They are not in third_party directory, so they should start with BAZEL.
--
Change-Id: I68b561ef8d06f50e8223af432a4f8aceb1a9c09d
Reviewed-on: https://bazel-review.googlesource.com/#/c/2670/
MOS_MIGRATED_REVID=112173485
|
|
|
|
|
|
|
| |
This is a prerequisite to making some changes to PackageFunction that require handling another exception.
--
MOS_MIGRATED_REVID=112172100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
just warn if a target turns out to not be present. This means that queries may return unexpected results. For instance, if "query" means "bazel query --order_output=no ", then here are the results of two queries:
query --universe_scope=//foo/... //foo:output_file
//foo:output_file
query --universe_scope=//foo/... deps(//foo:output_file)
WARNING: Targets not in graph [//foo:output_file generated_file]
//foo:output_file
--
MOS_MIGRATED_REVID=112163475
|
|
|
|
|
|
|
| |
some recent profiling.
--
MOS_MIGRATED_REVID=112161558
|
|
|
|
|
|
|
| |
targeting Apple platforms.
--
MOS_MIGRATED_REVID=112152418
|
|
|
|
|
|
|
| |
environments of runtime tools.
--
MOS_MIGRATED_REVID=112149571
|
|
|
|
|
|
|
|
|
|
|
| |
statements work in remote repositories.
This work is somewhat sisyphean; the principled thing to do would be to just do this resolution when labels are parsed.
Fixes #783.
--
MOS_MIGRATED_REVID=112137996
|
|
|
|
|
|
|
| |
the tests (which spawn multiple tests in the outside Bazel instance with each its own inner Bazel instance which in turn have their own thread pool) doesn't grind the machine to a halt.
--
MOS_MIGRATED_REVID=112132298
|
|
|
|
|
|
|
|
|
| |
Using java8-jdk will match both openjdk-8-jdk and oracle-java8-jdk similarly with java7-jdk. If
either of them are installed on the system allowing bazel to be installed in either case. Also the jdk source is not needed to create the bazel deb pacakge.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/785
MOS_MIGRATED_REVID=112132285
|
|
|
|
|
|
|
| |
It isn't necessary anymore.
--
MOS_MIGRATED_REVID=112132272
|
|
|
|
|
|
|
|
| |
See https://groups.google.com/forum/#!topic/bazel-discuss/xPe-oaqWZ6s
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/787
MOS_MIGRATED_REVID=112129205
|
|
|
|
|
|
|
|
|
|
|
|
| |
The ConfiguredTargetFunction can only throw a NoSuch{Target,Package}Exception
if it's run for a non-existent target. However, it will never request a CT for
a non-existent target: all labels are run through DependencyResolver in order
to determine the configuration transition, which requires loading the target.
If it doesn't exist, the label is never returned from the DependencyResolver,
and errors are swallowed (we rely on the loading phase to report the error).
--
MOS_MIGRATED_REVID=112127012
|
|
|
|
|
|
|
| |
This test was timing out on ci.bazel.io: http://ci.bazel.io/job/Bazel/JAVA_VERSION=1.7,PLATFORM_NAME=linux-x86_64/298/console
--
MOS_MIGRATED_REVID=112126463
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112099756
|
|
|
|
|
|
|
|
|
| |
Testing seems to have shown that the original reason for this being needed
(running out of file handles due to unclosed file streams) has been fixed,
meaning we don't need the GC workaround anymore.
--
MOS_MIGRATED_REVID=112088923
|
|
|
|
|
|
|
| |
avoid silly stack overflow when getting the object's hash code or string representation.
--
MOS_MIGRATED_REVID=112085348
|
|
|
|
|
|
|
| |
This is necessary for propagating the catastrophic exception so that it is available at the top level.
--
MOS_MIGRATED_REVID=112083848
|
|
|
|
|
|
|
| |
WalkableGraphFactory interface with a hook to inform the factory when the WalkableGraph is done being used.
--
MOS_MIGRATED_REVID=112074284
|
|
|
|
|
|
|
|
|
|
|
| |
Native rule classes can provide default values for rules after they're
deserialized, so there isn't a need to serialize those default values.
This doesn't apply yet to rules with Skylark-defined rule classes, due
to the non-serializablity of Skylark rule classes.
--
MOS_MIGRATED_REVID=112066930
|
|
|
|
|
|
|
|
|
| |
TargetPatternKey, since that is what is needed by callers.
Also, since the PathFragments come from packages, they are guaranteed to be well-formed, so the checks we were doing were unnecessary.
--
MOS_MIGRATED_REVID=112059930
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112042343
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112039216
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
repository where the package group is.
There is currently no way to refer to packages in other repositories and that doesn't seem to be useful, because visibility currently checks the repository name in the label and that can be changed in the main WORKSPACE file. If needed, it'd be pretty easy to implement, though.
As a drive-by fix, made the parsing of the package name call into the same logic implemented in the cmdline package because code duplication is bad, mmmkay?
Fixes #767.
--
MOS_MIGRATED_REVID=112032508
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112027856
|
|
|
|
|
|
|
|
|
| |
repository-local.
Fixes #765.
--
MOS_MIGRATED_REVID=112027627
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112027454
|
|
|
|
|
|
|
| |
version.
--
MOS_MIGRATED_REVID=111978539
|
|
|
|
|
|
|
| |
This will allow Skylark rules to interact nicely with cc_inc_library rules.
--
MOS_MIGRATED_REVID=111969252
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=111959966
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This used to cause spurious rebuilds because the timestamp (which was
changed every server restart) is used for deciding whether the file
changed or not.
Closes #573
--
Change-Id: I0e95910353426b22b61a3573ca7465e1edcedaac
Reviewed-on: https://bazel-review.googlesource.com/#/c/2390/
MOS_MIGRATED_REVID=111953023
|
|
|
|
|
|
|
|
|
| |
Without those dependencies, scala builds fails with sandboxing enabled
--
Change-Id: I64d262ada6ab3df210e72eba53305febecfbdbaa
Reviewed-on: https://bazel-review.googlesource.com/#/c/2660/
MOS_MIGRATED_REVID=111952523
|
|
|
|
|
|
|
| |
RELNOTES:
--
MOS_MIGRATED_REVID=111951279
|
|
|
|
|
|
|
| |
Variables docs for remaining Bazel rule classes.
--
MOS_MIGRATED_REVID=111947479
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=111946969
|
|
|
|
|
|
|
| |
apkbuilder.
--
MOS_MIGRATED_REVID=111935178
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By default wrapping can split on `-` characters which creates the chance that any
dependency with a `-` in it that falls near the wrap threshold will get
split along two lines and render the control file invalid.
> Text is preferably wrapped on whitespaces and right after the hyphens
> in hyphenated words; only then will long words be broken if necessary,
> unless TextWrapper.break_long_words is set to false.
https://docs.python.org/3.1/library/textwrap.html#textwrap.TextWrapper.break_long_words
Fixes #772.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/777
MOS_MIGRATED_REVID=111925490
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In general the external integration tests shouldn't need to reset state
between tests, but test_fetch is explicitly assuming a clean environment
to start off with. Fixes #769 (I think, I can't actually test it due to #770).
Change-Id: I63eef924c5b7bff3225c6b67a300d57a7675aeda
--
Change-Id: I63eef924c5b7bff3225c6b67a300d57a7675aeda
Reviewed-on: https://github.com/bazelbuild/bazel/pull/771
MOS_MIGRATED_REVID=111893662
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=111892954
|
|
|
|
|
|
|
|
|
| |
modifications to remove deprecation warnings, to create deterministic apks (removes timestamps), and to make calling ApkBuilder more convenient.
RELNOTES: Timestamps within Android apks are removed to make apks deterministic.
--
MOS_MIGRATED_REVID=111890659
|
|
|
|
|
|
|
| |
Fixes #770 to an acceptable extent.
--
MOS_MIGRATED_REVID=111889925
|
|
|
|
|
|
|
|
|
|
| |
0.1.3 was transformed into 0.1.~3 instead of 0.1.3
Tested the regexp manually with:
echo 0.1.3 | sed ...
echo 0.1.3rc3 | sed ...
--
MOS_MIGRATED_REVID=111884245
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=111869417
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=111866202
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
./compile.sh is giving:
$ ./compile.sh build bazel-bin/src/bazel
🍃 Building Bazel with Bazel.
INFO: Found 1 target...
INFO: From Compiling src/main/cpp/blaze.cc:
In file included from src/main/cpp/blaze.cc:58:
./src/main/cpp/blaze_globals.h:42:1: warning: 'GlobalVariables' defined as a struct here but previously declared as a class [-Wmismatched-tags]
struct GlobalVariables {
^
./src/main/cpp/blaze_abrupt_exit.h:23:1: note: did you mean struct here?
class GlobalVariables;
^~~~~
struct
1 warning generated.
--
MOS_MIGRATED_REVID=111863702
|
|
|
|
|
|
|
| |
from the current package batch.
--
MOS_MIGRATED_REVID=111858978
|
|
|
|
|
|
|
|
|
| |
The installer was missing the StdRedirect.dylib after a recent change.
This was breaking the Tutorial job on ci.bazel.io (and iOS builds using
that installer).
--
MOS_MIGRATED_REVID=111855462
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=111854804
|