| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
This target include all non tests targets of Bazel to do integration tests of
bootstrapping.
--
MOS_MIGRATED_REVID=115830741
|
|
|
|
|
|
|
|
|
|
| |
Win32 have no good API for that (basically we need to resort to ioctl
call). Shelling out to mklink.
Needed for #276.
--
MOS_MIGRATED_REVID=115040968
|
|
|
|
|
|
|
|
|
| |
cygwin lies about it, stripping the '.exe' suffix.
Needed for #276.
--
MOS_MIGRATED_REVID=114860126
|
|
|
|
|
|
|
|
|
| |
for a long time.
RELNOTES: The --skyframe flag is no longer available for the build command.
--
MOS_MIGRATED_REVID=113947409
|
|
|
|
|
|
|
|
|
|
|
| |
This is the only variable we need to propagate to bootstrap Bazel.
We might need to have a more principled approach for this, e.g. for
MakeVariables.
Needed for #276.
--
MOS_MIGRATED_REVID=113777759
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=113764325
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=113556731
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=113366155
|
|
|
|
|
|
|
|
|
|
|
|
| |
The consumers of Connect() function are just interested in knowning if
it has connected or not ("Did we connect?"). Leave the check for zero as
implementation detail of this function, making the callsites not having
to repeat the condition themselves.
--
Change-Id: Idc327c681c5defbb27039cd170f32d5ebd0e0a32
Reviewed-on: https://bazel-review.googlesource.com/#/c/2750/
MOS_MIGRATED_REVID=113040325
|
|
|
|
|
|
|
|
|
| |
ParseOptions() function does not return any value (its type is void).
--
Change-Id: I7e3b818169a304cc2ad6c8d1580ce010b7d79d12
Reviewed-on: https://bazel-review.googlesource.com/#/c/2740/
MOS_MIGRATED_REVID=112762600
|
|
|
|
|
|
|
|
|
|
|
| |
It is counter-intuitive to read ConnectToServer(false). By having
/*start=*/ in front of the boolean parameter the intention gets clear
(i.e., if it should or not start the Java server).
--
Change-Id: I74847deb6ec7daba62facd7a746d418943448182
Reviewed-on: https://bazel-review.googlesource.com/#/c/2680
MOS_MIGRATED_REVID=112466249
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
./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
|
|
|
|
|
|
|
| |
bazel server exits abruptly.
--
MOS_MIGRATED_REVID=111641619
|
|
|
|
|
|
|
| |
shim is done, and Blaze now always preserves spaces in host_jvm_args.
--
MOS_MIGRATED_REVID=111523524
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=111429102
|
|
|
|
|
|
|
|
| |
The product is now named bazel and that's the binary people have installed.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/737
MOS_MIGRATED_REVID=111071899
|
|
|
|
|
|
|
|
|
| |
The old behavior can still be achieved by passing --noexperimental_preserve_spaces_in_host_jvm_args, but that will go away after a release.
Oh, also enable the option --noexperimental_preserve_spaces_in_host_jvm_args -- turns out we don't get negative booleans automatically.
--
MOS_MIGRATED_REVID=110816311
|
|
|
|
|
|
|
| |
problematic if a .bazelrc file specifies an option that is allowed to be repeated, duplicates of that option are problematic (one example is http://bazel.io/docs/bazel-user-manual.html#flag--per_file_copt).
--
MOS_MIGRATED_REVID=110689696
|
|
|
|
|
|
|
|
|
| |
$OUTPUT_BASE/execroot/<workspace name> instead of $OUTPUT_BASE/<workspace name>.
This makes it possible to run Bazel in directories whose name clashes with one of the pre-existing files in the output base. Note that this option is turned off by default for now.
--
MOS_MIGRATED_REVID=109791053
|
|
|
|
|
|
|
|
|
| |
The code changes are mostly due to dslomov, not me, although I refactored
the Jvm class a bit based on his changes. I set dslomov as the author.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/688
MOS_MIGRATED_REVID=109536553
|
|
|
|
|
|
|
| |
RELNOTES[NEW]: .bazelrc allows workspace-relative imports as "import %workspace%/path/to/rcfile"
--
MOS_MIGRATED_REVID=109237460
|
|
|
|
|
|
|
| |
now deprecated. Pass each JVM option behind its own --host_jvm_args flag.
--
MOS_MIGRATED_REVID=108085362
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108029812
|
|
|
|
|
|
|
|
|
| |
through to the JVM instead of (almost certainly incorrectly) splitting the options along spaces.
This allows us to pass non-quote-delimited strings to the JVM, which is necessary for things like -XX:OnOutOfMemoryError="kill -3 %p" (normally bash strips those quotes, but they're not stripped when passed via --host_jvm_args).
--
MOS_MIGRATED_REVID=107820087
|
|
|
|
|
|
| |
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/571
MOS_MIGRATED_REVID=107471259
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106605250
|
|
|
|
|
|
|
|
|
| |
back to getpwuid())
Also a minor compatibility fix in a sed invocation.
--
MOS_MIGRATED_REVID=106291639
|
|
|
|
|
|
|
| |
server death" implementation. Boost grace period on SIGKILL to 10s.
--
MOS_MIGRATED_REVID=106080991
|
|
|
|
|
|
|
|
|
|
|
| |
running server (because startup flags changed, different Blaze version, etc.). Currently, we do a SIGTERM then fallback to a SIGKILL. Our logic to check if the server was still up after the fallback was backwards, so in some cases we would connect to the old server even though we just sent it a SIGKILL. Not really ideal.
Note that this only occurred if the SIGTERM failed to kill the Blaze process within 10s, so this failure mode happened rarely.
Also: Check for the expected errno from the kill(), and exit with an "internal error" exit code instead of "1" if we are unable to kill the old server.
--
MOS_MIGRATED_REVID=105999230
|
|
|
|
|
|
|
| |
A previous commit caused install_base_key to be a large .zip file instead of 32 alphanumeric characters. Thus, when Bazel tried to extract itself, it tried to create a directory of the name "$INSTALL_BASE/<40M path segment>/<long path>", and it allocated said 40M each time it walked up a path segment trying to create parent directories.
--
MOS_MIGRATED_REVID=105600489
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105504785
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
This is causing segfaults.
*** Original change description ***
Remove copy ctor and operator= from BlazeStartupOptions
--
MOS_MIGRATED_REVID=104726824
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104688018
|
|
|
|
|
|
|
| |
--invocation_policy startup flag and allows an application invoking Bazel to set or override flag values (whether from the command line or a bazelrc).
--
MOS_MIGRATED_REVID=104160290
|
|
|
|
|
|
|
|
|
|
|
| |
With the toolchain under Wheezy (GCC 4.7.2 and binutils 2.22), using
both -fPIE and -fPIC does not create pic object files, which the build
of Bazel seems to expect as of ee8fcd312eef51d2558c940f00d6381af0d52dff.
--
Change-Id: I0a33d1bc6dc0e3cdcffb473d4e78dac1a6b8ab41
Reviewed-on: https://bazel-review.googlesource.com/#/c/1690/
MOS_MIGRATED_REVID=104093416
|
|
|
|
|
|
|
| |
It seems unused, and the Bazel dashboard is more useful, as can persist results.
--
MOS_MIGRATED_REVID=104085798
|
|
|
|
|
|
|
|
|
|
|
| |
The headers were modified with
`find . -type f -exec 'sed' '-Ei' 's|Copyright 201([45]) Google|Copyright 201\1 The Bazel Authors|' '{}' ';'`
And manual edit for not Google owned copyright. Because of the nature of ijar, I did not modified the header of file owned by Alan Donovan.
The list of authors were extracted from the git log. It is missing older Google contributors that can be added on-demand.
--
MOS_MIGRATED_REVID=103938715
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103087492
|
|
|
|
|
|
|
|
|
| |
Previously the logger output was sent out to the console,
leading to garbage information in batch mode. Now, the log
are sent to a log file in the output base.
--
MOS_MIGRATED_REVID=102989990
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was printing:
src/main/cpp/blaze_util.cc: In function 'bool blaze::WriteFile(const string&, const string&)':
src/main/cpp/blaze_util.cc:211:28: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
return r == content.size();
^
src/main/cpp/blaze_util.cc: In function 'bool blaze::CheckJavaVersionIsAtLeast(const string&, const string&)':
src/main/cpp/blaze_util.cc:334:41: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
for (i = 0; i < jvm_version_vect.size() && i < version_spec_vect.size();
^
src/main/cpp/blaze_util.cc:334:73: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
for (i = 0; i < jvm_version_vect.size() && i < version_spec_vect.size();
^
src/main/cpp/blaze_util.cc:344:34: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
if (i < version_spec_vect.size()) {
^
src/main/cpp/blaze_util.cc:345:39: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
for (; i < version_spec_vect.size(); i++) {
This also fixes that we weren't checking write()'s return code.
--
MOS_MIGRATED_REVID=102656105
|
|
|
|
|
|
|
|
| |
I had to comment out a couple of tests, I don't know why they're not passing
right now.
--
MOS_MIGRATED_REVID=102535967
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is not really nice, there are several hacks there. This
repository will get removed in the future and linked to a
remote one instead. I tested it against the tutorial and
it works like a charm. mobile-install seems like to work,
maybe that's also fixing the last issue reported in #392.
Known issue: Java compilation output errors about files being
modified in the future.
--
MOS_MIGRATED_REVID=102282979
|
|
|
|
|
|
|
| |
--
Change-Id: I4e65cc583e758d2f7e45209ffcb37f6a871e2ed7
Reviewed-on: https://bazel-review.git.corp.google.com/#/c/1840
MOS_MIGRATED_REVID=101462155
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101218746
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=100609863
|
|
|
|
|
|
|
| |
--
Change-Id: I36b096cfdf7b150121809ff5b07c74eac1cbf7ad
Reviewed-on: https://bazel-review.git.corp.google.com/#/c/1771
MOS_MIGRATED_REVID=100573875
|
|
|
|
|
|
|
| |
embedded binaries.
--
MOS_MIGRATED_REVID=100476182
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
exec(3) under mingw converts every command line argument that looks like Unix path
into Windows path when executing non-mingw images (criteria for non-mingw image is
that the image does not depend on msys-<version>.dll). This affects bazel labels
(`//foo:bar` becomes `/foo:bar` for example).
This CL:
1) Replaces usage of execv(3) with Windows-native CreateProcess.
2) Converts all command line arguments that are indeed paths into Windows paths.
--
MOS_MIGRATED_REVID=100386350
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=100109450
|