| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The old implementation cached the timestamp when the workspace status
action is created, which may be much earlier then the action gets
executed and end up leaving stale timestamp in volatile-status.
Close #1103
--
Change-Id: I0f09ac66681a134aeb10daf2455f3c3f98d8cd8f
Reviewed-on: https://bazel-review.googlesource.com/#/c/3221/
MOS_MIGRATED_REVID=119930493
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119920313
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119902657
|
|
|
|
|
|
|
|
|
| |
cc_* targets, CcLibraryHelper will not process objc source files, which may have been provided accidentally though a filegroup.
Note: This is note intended to prevent illegal sources for cc_* targets - that will be implemented in a different CL. This will involve making changes to filtering occuring in CcCommon, which for now will permit objc source.
--
MOS_MIGRATED_REVID=119897621
|
|
|
|
|
|
|
|
|
| |
It is probably more efficient in the common case where the Iterable is a collection. String and list handling in Skylark results in a *lot* of calls to this method, and the use of addAll should reduce the amount of copying and GCing that needs to occur.
An alternative would be to change the underlying type of SkylarkList from ArrayList to LinkedList, which would reduce the copying and GCing due to list concatenation even more. There is probably a downside to that but it is not clear if it is significant.
--
MOS_MIGRATED_REVID=119891128
|
|
|
|
|
|
|
| |
processing.
--
MOS_MIGRATED_REVID=119873729
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119868282
|
|
|
|
|
|
|
|
|
| |
on Windows
--
Change-Id: I0048202b431ca05b88f67153389ca40c1542b1d5
Reviewed-on: https://bazel-review.googlesource.com/#/c/3371
MOS_MIGRATED_REVID=119861292
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119848254
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119843072
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119832385
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Note that the presence of server/grpc_port does not guarantee that the server actually listens to it and we can't guarantee it, either, because it can always be kill -9'd.
I haven't decided yet how the transition between AF_UNIX and gRPC will work. For now, I'm happy that we can start up a Java server.
The way to get the kernel-chosen port is truly awful, but it is apparently impossible to do so in a different way:
https://github.com/grpc/grpc-java/issues/72
--
MOS_MIGRATED_REVID=119828354
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Contributor finds some bugs and after fixing some bugs there are more bugs to fix now.
*** Original change description ***
Mount whole directories into the sandbox when possible
This halves the overhead with sandboxing enabled vs disabled for a test
that basically only mounts a bunch of files out of a directory, and
slows that same test with a single extra file added to the directory
(but not mounted) by only ~4%.
The test is <https://gist.github.com/bsilver8192/10527a862ce16bb7f79a>
with 30000 inputs moved to a subdirectory and on...
***
ROLLBACK_OF=119138157
--
MOS_MIGRATED_REVID=119828267
|
|
|
|
|
|
|
|
|
|
|
|
| |
While the timing assumptions in those tests were quite generous (a sleep
10 should not take 15s, an event supposed to happen every second should
be observed at least once in a 3 second interval), it seems that under
really heavily loaded test environments those assumptions do not hold
true. So remove the tests, as it is better to not have integration tests
for timing properties than to have flaky ones.
--
MOS_MIGRATED_REVID=119826405
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119813568
|
|
|
|
|
|
|
| |
Remove ArtifactFile, which is rendered obsolete by TreeFileArtifact.
--
MOS_MIGRATED_REVID=119789154
|
|
|
|
|
|
|
| |
skylark native access to ObjcProvider instances.
--
MOS_MIGRATED_REVID=119782586
|
|
|
|
|
|
|
|
|
| |
third_party.
I'm confused that Bazel has the concept of third_party, but as long as it does, let's exploit it.
--
MOS_MIGRATED_REVID=119779306
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks ci.bazel.io
While the basics for fixing the build is easy (just a few typos in packages building), fixing the test is a bit more tricky. I see only one solution for fixing the test: use a select statement that would select the good bazel version but that would always pull JavaBuilder as an external dependency when we do test.
Better roll this back then check the JavaBuilder 0.1.0 as a binary in third_party before rolling forward (a similar change is still needed to decouple running the test and building the binary for JDK 7)
*** Original change description ***
Refactor build for JDK 7
Now the JDK 7 tuning happens all in Bazel, removing logic
from the CI script. It uses remote repositories to access
JDK 7 dependencies.
--
MOS_MIGRATED_REVID=119773123
|
|
|
|
|
|
|
| |
rolled back in commit 1250fdac4c7769cfa200af8b4f9b061024356fea. There was nothing wrong with that change.
--
MOS_MIGRATED_REVID=119756383
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119755803
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
src/main/java/com/google/devtools/build/lib/exec/SymlinkTreeHelper.java:
enable --windows_compatible flag on Windows to make build-runfiles.exe work.
scritps/bootstrap/compile.sh:
--windows_compatible will also be passed to a dummy build-runfiles.exe defined in complie.sh.
Which is actully a batch script, modify it to make it work.
-----
With the changes above, we are able to build bazel with bazel. But when you try to
run ./compile.sh compile /path/to/bazel again without clean up tmp directory, it will fail with
a permission deny error. The reason seems to be that you can't use build-runfile.exe to build the
same hard link twice, still trying to solve that.
--
Change-Id: I93340b1ba9fa415f6db963b106e264799e33ede3
Reviewed-on: https://bazel-review.googlesource.com/#/c/3334
MOS_MIGRATED_REVID=119751076
|
|
|
|
|
|
|
| |
RELNOTES: java_import now allows its 'jars' attribute to be empty.
--
MOS_MIGRATED_REVID=119749103
|
|
|
|
|
|
|
|
|
|
|
| |
Whenever an event has to be reported to the scroll-back buffer, the old progress
bar has to be removed first. Afterwards, it is redrawn. In a setting without
cursor control, this, however, litters the log with lots status bars. Therefore,
only redraw the progress bar after an event if cursor control is available. Note
that the refresh thread will eventually ensure an up-to-date progress bar anyway.
--
MOS_MIGRATED_REVID=119737382
|
|
|
|
|
|
|
| |
rules.
--
MOS_MIGRATED_REVID=119737046
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the experimental UI, show the most recent finished test in the (long) progress bar.
For failed test, immediately write an entry to the scroll-back buffer. In this
way, the user can get an already investigate test failures while other tests are
still running.
--
Change-Id: I5df29dc55b979c8547e99e9ac3f60563736b48e8
Reviewed-on: https://bazel-review.googlesource.com/#/c/3351
MOS_MIGRATED_REVID=119732631
|
|
|
|
|
|
|
|
|
|
|
| |
When running tests, a useful information to know is the number of tests
that have passed and failed already. Hence subscribe to the relevant events
and provide this information in the progress bar as well.
--
Change-Id: I6fabec3f4585500f096b820dbbd5e8e6897647fa
Reviewed-on: https://bazel-review.googlesource.com/#/c/3350
MOS_MIGRATED_REVID=119727962
|
|
|
|
|
|
|
| |
c++ rule implementation backend and an OSX crosstool.
--
MOS_MIGRATED_REVID=119660101
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119655452
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119653212
|
|
|
|
|
|
|
|
|
|
|
| |
The last version of the status bar will drop into the scroll-back
buffer. Hence it should really represent the final state. To achieve
this, ignore the refresh limit on the progress bar for its final update.
--
Change-Id: I50b327dca80c12c9373e59a8702063369b18c461
Reviewed-on: https://bazel-review.googlesource.com/#/c/3333
MOS_MIGRATED_REVID=119637626
|
|
|
|
|
|
|
|
|
| |
--sandbox_debug and --verbose_failures are on. See discussion in #1049.
RELNOTES:
--
MOS_MIGRATED_REVID=119635080
|
|
|
|
|
|
|
|
|
|
|
| |
Now the JDK 7 tuning happens all in Bazel, removing logic
from the CI script. It uses remote repositories to access
JDK 7 dependencies.
--
Change-Id: Iff590c6642ca5b2343aa15096f8fd837d1c80787
Reviewed-on: https://bazel-review.googlesource.com/#/c/3327
MOS_MIGRATED_REVID=119634530
|
|
|
|
|
|
|
| |
and bind().
--
MOS_MIGRATED_REVID=119633865
|
|
|
|
|
|
|
|
| |
As part of that, move a BinTools and the WorkspaceStatusActionFactory to the
BlazeWorkspace.
--
MOS_MIGRATED_REVID=119633702
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119631623
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
--
MOS_MIGRATED_REVID=119625653
|
|
|
|
|
|
|
|
|
|
| |
Broken by commit a6ae3e7a, which added sysctlbyname() without
required headers.
While there, remove unused PATH_MAX2.
--
MOS_MIGRATED_REVID=119619207
|
|
|
|
|
|
|
| |
There's second implementation a few lines below.
--
MOS_MIGRATED_REVID=119618086
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119609967
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119599941
|
|
|
|
|
|
|
|
|
| |
come up a couple of times.
RELNOTES:
--
MOS_MIGRATED_REVID=119578035
|
|
|
|
|
|
|
| |
can process class jars generated with javacopts=["-parameters"].
--
MOS_MIGRATED_REVID=119568210
|
|
|
|
|
|
|
| |
point to the workspace root.
--
MOS_MIGRATED_REVID=119558172
|
|
|
|
| |
MOS_MIGRATED_REVID=119557016
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119533501
|