| Commit message (Collapse) | Author | Age |
|
|
|
| |
PiperOrigin-RevId: 185381597
|
|
|
|
| |
PiperOrigin-RevId: 185215813
|
|
|
|
|
|
| |
codec, but whose parent classes have codecs. This is ok because the polymorphic strategy doesn't need an instance of the grandchild class: the parent class is fine, so long as it has a codec.
PiperOrigin-RevId: 185200943
|
|
|
|
| |
Change-Id: Id636879aeab94916fcaed3c067e4077215ebc6df
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a rollforward with fixes.
The values (if present) are written into the manifest with this format:
Target-Label: <label>
Injecting-Rule-Kind: <kind>
In the future, JavaBuilder will make sure of this instead of command line arguments to find owners for jars for its add_dep commands.
PiperOrigin-RevId: 185159950
|
|
|
|
| |
PiperOrigin-RevId: 185153485
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Cascade rollback to unbreak bazel tests
*** Original change description ***
Update ijar tests to verify time stamp.
***
PiperOrigin-RevId: 185147605
|
|
|
|
| |
PiperOrigin-RevId: 185009133
|
|
|
|
|
|
|
|
|
|
|
| |
The values (if present) are written into the manifest with this format:
Target-Label: <label>
Injecting-Rule-Kind: <kind>
In the future, JavaBuilder will make sure of this instead of command line arguments to find owners for jars for its add_dep commands.
PiperOrigin-RevId: 185006704
|
|
|
|
|
|
|
|
|
| |
instead of removing them, since builds that use modules need them to be
visible across compilation boundaries. Note that the module-infos don't
contain any implementation that needs to be removed, so ijar just copies
the entire file through.
PiperOrigin-RevId: 184562080
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 181149284
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
FreeBSD should work again, so re-enable it.
*** Original change description ***
Remove FreeBSD from our CI temporarily.
RELNOTES: None.
PiperOrigin-RevId: 181140165
|
|
|
|
| |
Change-Id: Ic3d2331b7ccb5ca7db6b0fe83a12c7a6d1b58a9a
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll forward of commit 86b4532769c22cca2ed7068a60f3326beaad34af after fixing bad import.
+small misc fixes suggested by critique
*** Original change description ***
Automated rollback of commit 86b4532769c22cca2ed7068a60f3326beaad34af.
*** Reason for rollback ***
Probably breaking //javatests/com/google/devtools/build/lib:Query2Tests
*** Original change description ***
Restructure how universeScope is used when testing configured query to mimick impending changes to the configured query interface (CL/179872445) which will pull build targets out of the query expression.
Fill in testTopLevelTransitions on the way!
PiperOrigin-RevId: 180930388
|
|
|
|
| |
Change-Id: I14256e583d07ebad9a0b525917d25e5cb5f7f684
|
|
|
|
|
|
|
|
| |
@damienmg Here are a few more changes. (`third_party` only)
Closes #4164.
PiperOrigin-RevId: 177278511
|
|
|
|
| |
PiperOrigin-RevId: 176987812
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use try-with-resources to close all streams.
I hope this will fix the spurious file deletion
failures on Windows, where the persistent
JavaBuilder worker cannot delete outputs from
previous builds because, supposedly, they are
still open, because a stale object that's ready
to be GC'd hasn't yet been actually GC'd.
Change-Id: Ia57b8bd0ba1b6ee0691d34467c92e86e35d4d71d
PiperOrigin-RevId: 175941520
|
|
|
|
|
|
| |
Closes #4052.
Change-Id: I30c4dc047195404a6ff63338ac4a944bb2755a1f
|
|
|
|
| |
PiperOrigin-RevId: 168789962
|
|
|
|
|
|
|
|
|
|
|
| |
Replace blaze_util::AsWindowsPathWithUncPrefix
with AsAbsoluteWindowsPath, which always returns
an absolute path.
Fixes https://github.com/bazelbuild/bazel/issues/2935
RELNOTES: none
PiperOrigin-RevId: 162727218
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In this commit:
- remove blaze::PrintError in favor of
blaze_util::PrintError
- remove Ijar's PrintLastErrorMessage in favor of
blaze_util::PrintError
- use pdie every time path conversion fails,
because that indicates a fatal error (bad user
input for a path flag, or downright bug)
- remove explicitly printing GetLastErrror; pdie
and PrintError do it already
- unify the pdie/PrintError message formats
Fixes https://github.com/bazelbuild/bazel/issues/2935
Change-Id: I5feaf73885cab95c43a28c529ada6942e037b162
PiperOrigin-RevId: 162587490
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 161785358
|
|
|
|
|
|
|
|
|
|
| |
Please refer to patch set 9 and its CI run for usage and test
results. In practice, users should create their own java_toolchain
rule in their project's BUILD file, and set the two attributes like
above instead of modifying //tools/jdk/BUILD.
Change-Id: Ic880f243086b00a58d453a8139ba4c957fe54bc7
PiperOrigin-RevId: 159694649
|
|
|
|
|
|
|
|
|
|
|
| |
This affects only the tuple that appears after 'if' inside a list
comprehension. Since a truth value is expected, it's very unlikely to break
existing code. It's technically a breaking change, but it's not worth
introducing a flag for this.
RELNOTES:
Parentheses around the tuple are now mandatory in [a for b in c if 1, 2]
PiperOrigin-RevId: 159218397
|
|
|
|
|
|
| |
This is part of https://bazel-review.googlesource.com/#/c/11590/.
Change-Id: Id4a7fd459013e3f25a5a99684ea04295e3b68fb4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change is a follow-up to a recent change which allowed LLVM raw profile files
to be directly used with blaze. This change allows zipped LLVM raw profile
files.
This uses //tools/zip:zipper to extract the zipped file contents.
This also adds a new option to //tools/zip:zipper, 'j', to junk directories while
unzipping.
Tested:
blaze test //devtools/blaze/integration:fdo_test
blaze test //third_party/ijar/test:zip_test
RELNOTES[NEW]: Zipped LLVM profiles are now supported.
PiperOrigin-RevId: 158849516
|
|
|
|
|
|
|
| |
This is a prerequisite for the next javac update, and mirrors the
approach used for other javac-based tests in Bazel (e.g.
BazelJavaCompilerTest).
PiperOrigin-RevId: 152779250
|
|
|
|
| |
PiperOrigin-RevId: 151461345
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Fixed all errors.
*** Original change description ***
Automated [] rollback of commit 69a127b8f4e353ecb163688ed3271fb47e0f385d.
--
PiperOrigin-RevId: 149092038
MOS_MIGRATED_REVID=149092038
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
[] has detected that 500 or more targets failed to build at commit 69a127b8f4e353ecb163688ed3271fb47e0f385d, each of which successfully built at the prior CL that affected them.
[] double-checked that //javatests/com/google/apphosting/tests/usercode:Security_StubTest
built at 148995024. The verification run was:
[]
but the same target failed to build at 148995025. The [] link for this run is available here: []
To see all targets that ran, along with their final status, visit: []
Questions? Comments? See the URL.
go/autorollback
*** Original change description ***
ijar: use bazel's file utilities
This change not only implements ijar for Windows
(with MSVC), but also fixes a bug in
mapped_file_windows (path conversion didn't make
the input path absolute, so we could not build
java code with the MSYS-less bazel).
Fixes https://github.com/bazelbuild/bazel/issues/2157
--
PiperOrigin-RevId: 148998092
MOS_MIGRATED_REVID=148998092
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change not only implements ijar for Windows
(with MSVC), but also fixes a bug in
mapped_file_windows (path conversion didn't make
the input path absolute, so we could not build
java code with the MSYS-less bazel).
Fixes https://github.com/bazelbuild/bazel/issues/2157
--
PiperOrigin-RevId: 148995025
MOS_MIGRATED_REVID=148995025
|
|
|
|
|
|
|
|
| |
--
Change-Id: I6ce9c6afe14dfaff8a60ae90ee1504684d9cc61c
Reviewed-on: https://cr.bazel.build/9117
PiperOrigin-RevId: 148891361
MOS_MIGRATED_REVID=148891361
|
|
|
|
|
|
|
|
| |
See https://github.com/bazelbuild/bazel/issues/2157
--
PiperOrigin-RevId: 148887981
MOS_MIGRATED_REVID=148887981
|
|
|
|
|
| |
PiperOrigin-RevId: 148768294
MOS_MIGRATED_REVID=148768294
|
|
|
|
|
|
|
|
|
|
|
| |
We may not assume that those are pulled in by other
header files; in fact, they are not on FreeBSD stable/11.
--
Change-Id: Ic976cc71968aab0a1c3d6652fe8d8f1c4afa480b
Reviewed-on: https://cr.bazel.build/8145
PiperOrigin-RevId: 143970238
MOS_MIGRATED_REVID=143970238
|
|
|
|
|
|
| |
Commit 6d31cb was an internal reorganization of google repository
that should have resulted in no change. Due to a bug in our export
process it deleted several files in third_party.
|
|
|
|
|
| |
PiperOrigin-RevId: 142666783
MOS_MIGRATED_REVID=142666783
|
|
|
|
|
|
|
|
| |
0 is not a valid DOS timestamp, days and months start at 1.
--
PiperOrigin-RevId: 141818782
MOS_MIGRATED_REVID=141818782
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 645dbc4 moved the file stating logic to
platform_utils.cc into the `stat_file` method,
then commit 8d6da00 added error reporting to that
method so callers wouldn't need to report errors
on their own. Problem is, one of the callers was
using stat_file for simple file existence checking
so reporting an error there was spurious.
Fixes https://github.com/bazelbuild/bazel/issues/2201
--
Change-Id: I40d1ee2bad8f3d03627c0b5c0bfd593bb5289d23
Reviewed-on: https://cr.bazel.build/7810
PiperOrigin-RevId: 141739581
MOS_MIGRATED_REVID=141739581
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We can now build //third_party/ijar/...:all with
--cpu=x64_windows_msvc.
We also have to use --output_user_root=/c/tmp
or something similarly short because
//third_party/zlib tickles https://github.com/bazelbuild/bazel/issues/2145
This change takes us closer to compiling Bazel
with MSVC.
See https://github.com/bazelbuild/bazel/issues/2107
--
PiperOrigin-RevId: 140846600
MOS_MIGRATED_REVID=140846600
|
|
|
|
|
|
|
|
|
|
|
|
| |
zip_main.cc no longer needs <unistd.h>.
This change takes us closer to compiling ijar,
thus Bazel, with MSVC.
See https://github.com/bazelbuild/bazel/issues/2157
See https://github.com/bazelbuild/bazel/issues/2107
--
MOS_MIGRATED_REVID=140724421
|
|
|
|
|
|
|
|
|
|
|
|
| |
zip_main.cc no longer needs <unistd.h>.
This change takes us closer to compiling ijar,
thus Bazel, with MSVC.
See https://github.com/bazelbuild/bazel/issues/2157
See https://github.com/bazelbuild/bazel/issues/2107
--
MOS_MIGRATED_REVID=140723658
|
|
|
|
|
|
|
|
|
|
|
| |
This change takes us closer to compiling ijar,
thus Bazel, with MSVC.
See https://github.com/bazelbuild/bazel/issues/2157
See https://github.com/bazelbuild/bazel/issues/2107
--
MOS_MIGRATED_REVID=140722341
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change takes us closer to compiling ijar,
thus Bazel, with MSVC.
Also update the StatFile method added by
unknown commit to report any errors.
See https://github.com/bazelbuild/bazel/issues/2157
See https://github.com/bazelbuild/bazel/issues/2107
--
MOS_MIGRATED_REVID=140719249
|
|
|
|
|
|
|
|
|
|
| |
This change takes us closer to compiling ijar,
thus Bazel, with MSVC.
See https://github.com/bazelbuild/bazel/issues/2107 and https://github.com/bazelbuild/bazel/issues/2157
--
MOS_MIGRATED_REVID=140717828
|
|
|
|
|
|
|
|
|
|
|
| |
The behavior of ftruncate on WSL is not same as standard Linux due to a bug, it'll fail on maped file.
This commit fix the bug by munmap the file before ftruncate.
Closes #2108.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2108
MOS_MIGRATED_REVID=140134115
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=135345337
|
|
|
|
|
|
|
| |
Those tests requires JDK8 features, just ignore them.
--
MOS_MIGRATED_REVID=135264862
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Other projects may depend on Ijar without wanting to depend on Bazel.
*** Original change description ***
Ijar: use utilities from Bazel's source
Remove a duplicate implementation of JoinPath.
--
MOS_MIGRATED_REVID=135088616
|