aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
* Refactor wrapper script msvc_tools.py to make path configure easilerGravatar Yun Peng2016-04-12
| | | | | | | | | Also fixed a small bug. -- Change-Id: I05dab2f4a5d6216f2972b0cd2cb62506f5b1cb06 Reviewed-on: https://bazel-review.googlesource.com/#/c/3326/ MOS_MIGRATED_REVID=119529809
* Don't make racy changes to the global Environment.FrameGravatar Brian Silverman2016-04-12
| | | | | | | | | | | | | | | 6f15335 Make labels in .bzl files in remote repos resolve relative [...] introduced a Frame#setLabel which is documented to create a new Frame but instead modifies the existing one. This results in the global environment being modified in-place. I've been seeing some strange errors about not finding various packages in the wrong repositories which seems to be fixed by this change. -- Change-Id: I9b8521e50f45cfd385b20491315904ff0e24dcf6 Reviewed-on: https://bazel-review.googlesource.com/#/c/3300 MOS_MIGRATED_REVID=119529142
* Keep output of experimental UI short if curses cannot be usedGravatar Klaus Aehlig2016-04-12
| | | | | | | | | | | | | | | | | | | | As the experimental UI should be usable in all situations, we also have to care about the situation where updating the status bar in place is not possible. In this case, we have to make sure we do not litter the output to much. To achieve this, - we use the short one-line version of the status bar, and - reduce the frequency for time-based updates. Unfortunately, this means that we have to further complicate the timing mechanisms for updating the progress bar. We now have 3 time intervals in place: - a short one, after which we update the progress bar, if we dropped an update due to too frequent events, - an intermediate one, describing the frequency of status bar updates due to time passing, and - a long one for purely time-based updates of the progress bar if we cannot update it in place. -- Change-Id: I5d59ba174c4d290b07181620e238362a8d21a6eb Reviewed-on: https://bazel-review.googlesource.com/#/c/3295 MOS_MIGRATED_REVID=119527089
* experimental_ui_test: avoid flakyness by disallow test cachingGravatar Klaus Aehlig2016-04-12
| | | | | | | | | | Under certain conditions it might happen that simultaenously running instances of the experimental_ui_test share cached results, leading to the (deliberatly) slow test taking shorter than tested for. Fix this by adding the --nochache_test_results options to the test run in the test. -- MOS_MIGRATED_REVID=119525789
* Disable warnings in protobuf.Gravatar Lukacs T. Berki2016-04-12
| | | | | | It's not our code, so we can't do much about them. Change-Id: If068995e494a398d2c8d05ba428c4d36dbc0e6a3
* Fix Bazel continuous build.Gravatar Lukacs Berki2016-04-11
| | | | | | | I carefully kept the test_rules.bzl file but managed to omit the corresponding BUILD file from the embedded tools zip. -- MOS_MIGRATED_REVID=119523076
* Add prefix to file path in ijar to allow file path longer than 260 on WindowsGravatar Yun Peng2016-04-11
| | | | | | | -- Change-Id: Ia176408e9b59caa85da7eb63fd3d9251a1d3fb40 Reviewed-on: https://bazel-review.googlesource.com/#/c/3328/ MOS_MIGRATED_REVID=119522458
* ExperimentalStateTracker: add a short version of the progress barGravatar Klaus Aehlig2016-04-11
| | | | | | | | | | | | When bazel is used without curses, every status message ever written will never be deleted and, instead, stick in the log. To keep the output manageable in this case, provide a one-line progress bar to be used in this case. -- Change-Id: Ia0f9619d406e676f88ff536617a56fd4990cb51e Reviewed-on: https://bazel-review.googlesource.com/#/c/3294 MOS_MIGRATED_REVID=119520912
* Support gRPC in the Bazel-internal protobuf rules.Gravatar Lukacs Berki2016-04-11
| | | | | -- MOS_MIGRATED_REVID=119518388
* Remove te protocol compiler rules from @bazel_tools.Gravatar Lukacs Berki2016-04-11
| | | | | | | | | | | | The immmediate reason for this change is that we also need to add gRPC support to the proto rules, and we don't want to also support gRPC in a half-baked way. This makes the Bazel binary much smaller and avoid giving false signals that we (for now) support protobuf compilation. The protobuf rules are only for compiling Bazel itself. RELNOTES[INC]: Bazel does not embed protocol buffer-related rules anymore. -- MOS_MIGRATED_REVID=119516246
* Rate limit updates in the experimental UI and keep it freshGravatar Klaus Aehlig2016-04-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Make the experimental UI honor the --show_progress_rate_limit flag. While just dropping a status bar update if it happens too soon after the last update shown would be easy, there are a few delecate points to keep in mind. Assume that several updates happen after another and then nothing for a long time. Then the last(!) update is the one the user wants to see, as it most accurately reflects which actions are running during the long period. However, the simple dropping algorithms would show the first of those state updates. So, whenever we refrain from updating due to the rate limit we to make sure that an update will happen soon-ish, even if no events are reported for a long time. We do this by having (at most) one thread that periodically triggers updates of the progress, if the rate limit allows this. This mechanism is additionally used to ensure that the progress bar, when showing time-dependent data is kept fresh. For this property we also add a test. There is a third point to keep in mind: users (and also our tests) want to see all phases. However, some phases (like loading) might be so short that they happen in its entirety within a refresh interval. Therefore, whenever a new important phase starts, we skip the rate limit interval once; note that this happens at most a fixed number of times during the entire build. -- Change-Id: Iee68194d7eb92d6ef9efdc7abde6f56edfa21ce8 Reviewed-on: https://bazel-review.googlesource.com/#/c/3293 MOS_MIGRATED_REVID=119515272
* experimental UI: only wrap lines if curses are usedGravatar Klaus Aehlig2016-04-11
| | | | | | | | | | | | | Lines are wrapped in the progress bar to reliably know how many lines we'll eventually have to erase (there are a couple of reasons for this; for example, the information about the terminal width often is unreliable). So, if we don't erase lines anyway, we can as well let the terminal break lines. -- Change-Id: Id20806e6d53bfeccc781200eeac96acf48a74b1d Reviewed-on: https://bazel-review.googlesource.com/#/c/3292 MOS_MIGRATED_REVID=119510906
* Do not emit compiler warning on zlib.Gravatar Lukacs Berki2016-04-11
| | | | | | | There are quite a few, and since the code base is quite stable and proven to work and is not out code anyway, there is no harm in ignoring them. -- MOS_MIGRATED_REVID=119507946
* experimental UI: honor --cursesGravatar Klaus Aehlig2016-04-11
| | | | | | | | | | | | Bazel can be asked to uses colors, but not to use other curses options. In this case, the ExperimentalEventHandler cannot rely on the terminal to ignore all curses output; hence it has to actively refrain from using curses that move the cursor. -- Change-Id: I026edade4366a8c5a8e56d376e8a4603f5c73b92 Reviewed-on: https://bazel-review.googlesource.com/#/c/3291 MOS_MIGRATED_REVID=119439855
* experimental UI: squeeze dots in last sample actionGravatar Klaus Aehlig2016-04-11
| | | | | | | | | | | | When showing the earliest started actions in the progress bar of the experimental UI, it is a wasted line to use a whole line just to show dots indicating that more actions are running; instead, just put the dots on the same line as the last action. -- Change-Id: I37fcb654f689786ab522036b563409b15b85437f Reviewed-on: https://bazel-review.googlesource.com/#/c/3290 MOS_MIGRATED_REVID=119439830
* Don't print extra newlinesGravatar Liam Miller-Cushon2016-04-11
| | | | | -- MOS_MIGRATED_REVID=119421719
* Properly use PrintStream in QueryCommand. PrintStream swallows all ↵Gravatar Nathan Harmata2016-04-11
| | | | | | | IOExceptions and so we need to check if any were encountered. -- MOS_MIGRATED_REVID=119417412
* Relax strict deps checking in Turbine, leave enforcement to JavaBuilderGravatar Liam Miller-Cushon2016-04-11
| | | | | -- MOS_MIGRATED_REVID=119394125
* Patch gRPC so that it compiles and works under msys2.Gravatar Lukacs T. Berki2016-04-11
| | | | | | The patch is being upstreamed, but for the time being, we need to maintain it in our source tree. Change-Id: I6a52dd0b0b57828030693dacdda23a906a2bee4f
* In RuleDefintion, use AutoValue and delete the checked-in generated code for it.Gravatar Carmi Grushko2016-04-08
| | | | | -- MOS_MIGRATED_REVID=119369970
* Allow Skylark repository rule to be privateGravatar Damien Martin-Guillerez2016-04-08
| | | | | | | | We want sometimes to wrap them around a macro and make it impossible to call them directly. So allow them to be private. -- MOS_MIGRATED_REVID=119362967
* Modify python template file to support WindowsGravatar Yun Peng2016-04-08
| | | | | -- MOS_MIGRATED_REVID=119361134
* Allow params files on Windows.Gravatar Lukacs Berki2016-04-08
| | | | | | | Windows currently means msys2, and the tools there do support params files, and BoringSSL cannot be compiled without them because command lines are too long. -- MOS_MIGRATED_REVID=119360154
* Run test in standalone mode with "local = 1". Fixes #1052.Gravatar Yue Gan2016-04-08
| | | | | -- MOS_MIGRATED_REVID=119351752
* ios_device attribute "xcode", which takes an "xcode_version" target to ↵Gravatar Chris Parsons2016-04-08
| | | | | | | | | select a specific xcode. RELNOTES: ios_device attribute "xcode", for declaring a specific xcode to use when selecting iOS simulators. -- MOS_MIGRATED_REVID=119317344
* Adds a small temporary hack to the Android resource processor so that it doesn'tGravatar Alex Humesky2016-04-08
| | | | | | | | | | error on a build tools version ending in "-preview", because the current version of the android_common libraries that bazel uses are slightly old and it will take some time to upgrade to the latest version, which know how to parse the new revision format. -- MOS_MIGRATED_REVID=119308647
* Adds the 64 bit library directory for aapt, aidl, and zipalign, which was addedGravatar Alex Humesky2016-04-08
| | | | | | | in Android SDK build tools version 24.0.0. -- MOS_MIGRATED_REVID=119305998
* Expose method on ruleContext for retrieving TransitiveInfoProviders by ↵Gravatar Chris Parsons2016-04-08
| | | | | | | | | configuration. This is useful for obtaining child split configurations and the information they provide. -- MOS_MIGRATED_REVID=119295699
* Provide ResourceShrinker with the generated R.java packages in addition to ↵Gravatar Andrew Pellegrini2016-04-08
| | | | | | | packages from manifests. This prevents resources from being removed when they have been generated into a package other than the one specified in their target's manifest. -- MOS_MIGRATED_REVID=119294591
* Don't emit native headers, only Java headersGravatar Liam Miller-Cushon2016-04-08
| | | | | | | If NATIVE_HEADER_OUTPUT is set (which it always was for ZipOutputFileManager), then javac will emit jni headers for native methods. Emitting the the headers requires doing unnecessary additional work and completing additional symbols, which may not be present on the classpath. -- MOS_MIGRATED_REVID=119286406
* Use AutoValue 1.2 instead of 1.0.Gravatar Carmi Grushko2016-04-07
| | | | | -- MOS_MIGRATED_REVID=119277579
* Fix bug introduced by commit dc0fbb42ab22ab8f3205b0884069e1ffe03677c9 where ↵Gravatar Nathan Harmata2016-04-07
| | | | | | | | | | | | | a less specific option specification in a rc file could override a more specific option specification when there's a non-trivial Command hierarchy. A concrete example would be a "build --foo=1" line overriding a "test --foo=2" line for a "test" invocation. See the added test for more details. Also fix some typos in BlazeCommandDispatcherRcoptionsTest.java. Note that commit dc0fbb42ab22ab8f3205b0884069e1ffe03677c9 was rolled back in commit 417dad0f1e0d0ed4ccd5f8e52b49eb79937da49d which also incidentally rolled back commit 4f0fbe1b09333806cce76b75214e98c7684766e0. So this change is effectively a roll-forward of both of those, plus the bug fix, plus the typo fixes, and plus a documentation update. -- MOS_MIGRATED_REVID=119276218
* Add msvc crosstool definitonGravatar Yun Peng2016-04-07
| | | | | | | | | | | | This patch add the msvc crosstool definiton to CROSSTOOL file and BUILD file. Two paths are expected to exist: for msvc: C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/ for windows sdk: C:/Program Files (x86)/Windows Kits/10/ -- Change-Id: I2b21e566a588459f9fef767c5dc9dab1565d1ae8 Reviewed-on: https://bazel-review.googlesource.com/#/c/3266 MOS_MIGRATED_REVID=119276027
* Add the wrapper script for msvc crosstoolGravatar Yun Peng2016-04-07
| | | | | | | | | | Using batch script to invoke real wrapper script written in python The default python path is expected to be C:/python_27_amd64/files/python.exe -- Change-Id: If47bf668ce4af2b6d28a1852189c061480816833 Reviewed-on: https://bazel-review.googlesource.com/#/c/3265 MOS_MIGRATED_REVID=119275909
* Rollback of commit 3248a5ea6ecb9f5f2080876a70de016825f54707.Gravatar Lukacs Berki2016-04-07
| | | | | | | | | | | | | *** Reason for rollback *** Breaks //src/test/shell/bazel:bazel_example_test because that relies on the protobuf rules depending on @bazel_tools . The correct solution is probably to eliminate the protobuf dependencies from @bazel_tools altogether, but let's make the continuous build green and then think. *** Original change description *** Update our rudimentary proto rules to be able to handle gRPC. -- MOS_MIGRATED_REVID=119271980
* Add a README.md for BoringSSL.Gravatar Lukacs Berki2016-04-07
| | | | | -- MOS_MIGRATED_REVID=119270465
* Use OPENSSL_NO_ASM for building BoringSSL.Gravatar Lukacs Berki2016-04-07
| | | | | | | Maybe a bit slower (but we aren't going to use SSL anytime soon anyway), but much less hassle with building. -- MOS_MIGRATED_REVID=119269169
* Update our rudimentary proto rules to be able to handle gRPC.Gravatar Lukacs Berki2016-04-07
| | | | | -- MOS_MIGRATED_REVID=119265313
* experimental UI: use LoadingProgressReceiverGravatar Klaus Aehlig2016-04-07
| | | | | | | | | | | | Subscribe to the LoadingPhaseStartedEvent to get the LoadingProgressReceiver; use it to provide information about the loading progress. As this event will not be raised by the LegacyLoadingPhaseRunner, do not depend on this event and still produce a sensible status bar if it is never raised. -- Change-Id: I1db24ceaf7de4fc42d00b02f470066cb38c877b4 Reviewed-on: https://bazel-review.googlesource.com/#/c/3270 MOS_MIGRATED_REVID=119261675
* Add Apache Commons Lang 2.6, for use with Apache Velocity 1.7Gravatar Carmi Grushko2016-04-07
|
* Remove the assembly source files for BoringSSL.Gravatar Lukacs T. Berki2016-04-07
| | | | | | Compiling with -DOPENSSL_NO_ASM yields slower crypto code, but we are not using that anyway (yet). Change-Id: I832bce7810d718a584f0bdd884e7f6958376d448
* Upgrade AutoValue from 1.0 to 1.2. Motivation: 1.2 has @AutoValue.BuilderGravatar Carmi Grushko2016-04-07
|
* Add README.bazel.md and BUILD files for gRPC.Gravatar Lukacs Berki2016-04-07
| | | | | -- MOS_MIGRATED_REVID=119260891
* Add error message for skylark for-else statement, and fix error message for ↵Gravatar Yue Gan2016-04-07
| | | | | | | single else statement. -- MOS_MIGRATED_REVID=119260729
* SkyframeExecutor: Raise an event at the beginning of the loading phaseGravatar Klaus Aehlig2016-04-07
| | | | | | | | | | | The main purpose of this event is to provide the LoadingProgressReceiver to any interested listener. Note that this event will only be raised if the option --experimental_skyframe_target_pattern_evaluator is given. -- Change-Id: Ic675c9e1255b7d60de28bdad1ec1838655abd389 Reviewed-on: https://bazel-review.googlesource.com/#/c/3269 MOS_MIGRATED_REVID=119258070
* Add the C++ gRPC implementation and the Java gRPC proto compiler plugin to ↵Gravatar Lukacs T. Berki2016-04-07
| | | | | | | | third_party . The Java code of gRPC is already there. Change-Id: I29091b11dc88a1946fd637fe678b269abfd8c035
* Update README.md and BUILD files for protobuf C++ sources v3.0.0-beta-2.Gravatar Lukacs Berki2016-04-07
| | | | | -- MOS_MIGRATED_REVID=119255585
* SkyframeExecutor: use a LoadingProgressReceiver during loading phaseGravatar Klaus Aehlig2016-04-07
| | | | | | | | | | In this way, information about the progress of the loading phase is collected. -- Change-Id: I80ff0c91e27f0b55780c18c05fbb4fdda93263d3 Reviewed-on: https://bazel-review.googlesource.com/#/c/3268 MOS_MIGRATED_REVID=119255431
* Add a LoadingProgressReceiver classGravatar Klaus Aehlig2016-04-07
| | | | | | | | | | Instances of this class keep track of the packages already loaded and those currently being loaded. This information can be useful for UIs. -- Change-Id: Ifd380dd2129d11181ad4a31ecbb71d142825df61 Reviewed-on: https://bazel-review.googlesource.com/#/c/3267 MOS_MIGRATED_REVID=119252784
* Remove mentions of the arm32 proto compiler and update README.md.Gravatar Lukacs Berki2016-04-07
| | | | | | | Information in README.md about the statically linked x86_64 binary and the src/ directory got lost due to a snafu with updating the tree from the Google-internal version. -- MOS_MIGRATED_REVID=119250383
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-01 14:45:59 +0000