aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
...
* Add a disabled test case that tickles a bug with the interaction of aspects ↵Gravatar Lukacs Berki2016-04-13
| | | | | | | and bind(). -- MOS_MIGRATED_REVID=119633865
* Refactor BlazeWorkspace creation to happen after BlazeRuntime construction.Gravatar Ulf Adams2016-04-13
| | | | | | | | As part of that, move a BinTools and the WorkspaceStatusActionFactory to the BlazeWorkspace. -- MOS_MIGRATED_REVID=119633702
* Make the genproto rules of Bazel usable from other repositories.Gravatar Lukacs Berki2016-04-13
| | | | | | | | | This is mainly so that Dash can be fixed. It's not the optimal solution because then Dash will pull in the whole Bazel repository for a tiny little part of it, though. The optimal solution would be to make Bazel use WORKSPACE dependencies and then factor it out to a separate repository, but this will be good enough to unbreak Dash for the time being. Progress toward fixing https://github.com/bazelbuild/dash/issues/12 . -- MOS_MIGRATED_REVID=119633183
* Make preprocessor modules mostly stateless; pass in the directories instead.Gravatar Ulf Adams2016-04-12
| | | | | -- MOS_MIGRATED_REVID=119631623
* Add stub gRPC C++ client and Java server.Gravatar Lukacs Berki2016-04-12
| | | | | | | The code doesn't do anything yet and it's unused code for now. This change only serves to add all the necessary dependencies to BUILD files that gRPC needs. -- MOS_MIGRATED_REVID=119628697
* Rollback of commit 351475627b9e94e5afdf472cbf465f49c433a25e.Gravatar Florian Weikert2016-04-12
| | | | | | | *** Reason for rollback *** -- MOS_MIGRATED_REVID=119625653
* Fix build on FreeBSD (again).Gravatar Piotr Sikora2016-04-12
| | | | | | | | | | Broken by commit a6ae3e7a, which added sysctlbyname() without required headers. While there, remove unused PATH_MAX2. -- MOS_MIGRATED_REVID=119619207
* testenv.sh.bazel: remove overridden function implementation.Gravatar Laszlo Csomor2016-04-12
| | | | | | | There's second implementation a few lines below. -- MOS_MIGRATED_REVID=119618086
* Remove some dead code.Gravatar Ulf Adams2016-04-12
| | | | | | | | The cast to Label can never succeed for a configured target node, so this code could never have been executed (or we'd see crashes at this location). -- MOS_MIGRATED_REVID=119615022
* Experimental UI test: deflake test_times_fresh().Gravatar Laszlo Csomor2016-04-12
| | | | | -- MOS_MIGRATED_REVID=119609967
* Fix missing format specifier.Gravatar Googler2016-04-12
| | | | | -- MOS_MIGRATED_REVID=119599941
* Prune anonymous classes in ijarGravatar Liam Miller-Cushon2016-04-12
| | | | | -- MOS_MIGRATED_REVID=119581073
* Document the difference between actions and genrules since the question has ↵Gravatar Dave MacLachlan2016-04-12
| | | | | | | | | come up a couple of times. RELNOTES: -- MOS_MIGRATED_REVID=119578035
* Increase ResourceShrinker MethodVisitor level to ASM5 from ASM4 so that it ↵Gravatar Andrew Pellegrini2016-04-12
| | | | | | | can process class jars generated with javacopts=["-parameters"]. -- MOS_MIGRATED_REVID=119568210
* RELNOTES[INC]: It is now an error for a cc rule's includes attribute to ↵Gravatar Janak Ramakrishnan2016-04-12
| | | | | | | point to the workspace root. -- MOS_MIGRATED_REVID=119558172
* --Gravatar Googler2016-04-12
| | | | MOS_MIGRATED_REVID=119557016
* Stop passing --strict_java_deps to header compilation actionsGravatar Liam Miller-Cushon2016-04-12
| | | | | | | | Turbine now leaves enforcement of strict deps to JavaBuilder. Compile-time dependencies will still be collected as long as --output_deps is set. -- MOS_MIGRATED_REVID=119551363
* exprimental_ui_test: set --show_progress_rate_limitGravatar Klaus Aehlig2016-04-12
| | | | | | | | | | The test on the freshness of the timing results depends on the show_progress_rate_limit; to avoid depending on defaults or rc-files, set it explicitly on the command line. While there, also move options before target name. -- MOS_MIGRATED_REVID=119535250
* Remove unnecessary warning when applying empty invocation policy.Gravatar Luis Fernando Pino Duque2016-04-12
| | | | | -- MOS_MIGRATED_REVID=119533501
* Batch package and subdirectory requests -- might as well avoid serializing ↵Gravatar Janak Ramakrishnan2016-04-12
| | | | | | | requests wherever we can. -- MOS_MIGRATED_REVID=119531512
* Make NoSuchTargetException a concrete class. Removed ↵Gravatar Googler2016-04-12
| | | | | | | | | BadWorkspaceFileException and BadPreludeFileException. BadWorkspaceFileException and BadPreludeFileException are not doing anythings special rather than providing a custom message. Replace them by using NoSuchTargetException directly. -- MOS_MIGRATED_REVID=119530878
* 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
generated by cgit v1.2.3 (git 2.39.1) at 2024-08-26 09:11:20 +0000