Skip to content

[pull] main from bazelbuild:master #450

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2,071 commits into
base: main
Choose a base branch
from
Open

Conversation

pull[bot]
Copy link

@pull pull bot commented May 20, 2023

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.1)

Can you help keep this open source service alive? 💖 Please sponsor : )

@pull pull bot added ⤵️ pull merge-conflict Resolve conflicts manually labels May 20, 2023
@pull pull bot requested a review from cpsauer May 20, 2023 02:12
sellophane and others added 27 commits February 25, 2025 15:40
Bug: 366128721
Test: n/a
Change-Id: I0ff314d4ea419d06cadf329c41e2be810d2d95ef

AOSP: d78a5589d270b4459fadc4e356921bce6a445e97

Co-authored-by: Googler <[email protected]>
1. as a pre-requisite also reduce the amount of details logged when
   the IDE is unable to find expected output artifacts.

2. drop artifact filtering support as it is rarely used and can filters
   can be applied afterwards.

Bug: 327638725
Test: n/a
Change-Id: Ibc4008f6340d7f08c6b220e871e9a3c1c090dd97

AOSP: 7fbfbd9ad4ed3a2b6b5da32fba25f5c4429a19bc

Co-authored-by: Googler <[email protected]>
Bug: n/a
Test: n/a
Change-Id: I6595886ea1cdd4590dc24b03083a8b6676649bb2

AOSP: 225cf7702db7ebc53648bf2698e54fc12ba523ac

Co-authored-by: Googler <[email protected]>
as it prevent migration to a different api.

Bug: n/a
Test: n/a
Change-Id: I93fa4f8a605409514f86e5ed354b058e71e323ec

AOSP: a069fba218da28dacea1cd3231287ffb538c40ca

Co-authored-by: Googler <[email protected]>
1. Builds may get multiple aspects applied resulting in multiple
   additional artifacts returned.

2. Make `getOutputGroupTargetArtifacts` return all artifacts declared by
   the target as its outputs instead of ambiguously defined direct
   artifacts, which in its current implementation is implementation
   dependent and returns top level named file sets only. Note, a single
   target may itself produce multiple nested file sets without
   participation of other targets at all. File sets basically follow the
   structure fo depsets. Perhaps the amount of logging in callers
   reflects the incorrect behavior.

3. When requesting `AndroidDeployInfo` from local build mirror the
   implementation providing support for remote builds and pass the
   output group name explicitly. note, these two implementations need
   to converged before they can be merged.

Bug: 385469770
Bug: 327638725
Test: existing
Change-Id: Idfb90474e74cd6e4fa9978452f687138c69df13c

AOSP: b228d1ef2bdb093b73203176ec8158061042505e

Co-authored-by: Googler <[email protected]>
…o avoid occurrence of backslashes on Windows (#7271)
* make cc compiler path exec root relative

* updated test for execroot changes

* fix external include paths

* forward compiler info messages properly

* update qsync test to collect issues during sync

* try to resolve catch2 headers in qsync test
instead of raw ParsedBepOutputs.  This is a step towards unifying them.

Bug: 327638725
Test: n/a
Change-Id: I23e3d9d0b4637ef8ac65458a4f4916f3e1dbd6a0

AOSP: 1c9f33b7a59023dd8e79a1092cbe23dfd149eedb

Co-authored-by: Googler <[email protected]>
to avoid misuse.

Bug: n/a
Test: n/a
Change-Id: I9e06e8c8eae748c381f381f111543ee4460dab1d

AOSP: f27d625a2c9a525fe23994e2b7b08acf0d004ee6

Co-authored-by: Googler <[email protected]>
Bug: 327638725
Test: BuildEventProtocolOutputReaderTest
Test: BuildEventProtocolOutputReaderLegacyTest
Change-Id: Ia54df932fbf5f6bf090c7810962b0996f335b910

AOSP: 37e18eda7680a8c01922353f88ebdde516fd76ff

Co-authored-by: Googler <[email protected]>
Bug: n/a
Test: n/a
Change-Id: I3bf09dfbf7b0123229056e30169878f618f7d6af

AOSP: abb8479a68846d6a51fe48c2d77617cd8cf182d2

Co-authored-by: Googler <[email protected]>
Bug: 363410313
Test: bazel test //tools/adt/idea/aswb/kotlin:integration_tests \
  --jvmopt="-Didea.kotlin.plugin.use.k2=true"
Change-Id: I81ef3129c7195d4795221b7847ae652ae7bcf173

AOSP: 0b0d5f4723ab9035155be4fbc3e3e9921fccad36

Co-authored-by: Googler <[email protected]>
mark Registry as loaded in non-application tests
1. There is nothing to do in the query sync mode
2. Rename classes to make sure they are not used in the query sync mode

Bug: 260643753
Test: n/a
Change-Id: I4b4eb7f61169bc8034ac69faeb4771d0cd090b81

AOSP: e604e90c8a4f583184fcf4ade5ad3b69c2e282f9

Co-authored-by: Googler <[email protected]>
When skipping finding artifact roots on the EDT we still need to
refresh these files.

Rename the experiment so it can be safely re-enabled (already done for
this name).

Bug: n/a
Test: n/a
Change-Id: Icb1043e0fc6181a53f68f0f5284c0e377e989c8d

AOSP: cd03c25523b886dc9686cc67199f17ee8270b913

Co-authored-by: Googler <[email protected]>
LeFrosch and others added 30 commits May 9, 2025 16:30
To avoid cache invalidation, pass options to the aspects using templating rather then defines.

fixes #7633
Project data directory might not be yet created when project is opened
and since it's not in patterns list, it's loaded to VFS and indexed by default.
However data there is not intended to be visible to user and not indexed,
so let's hide it too.
It is useless outside the Google environment
Its needMigration() can fail if .blazerc does not exist
Extracting tools.jar was possible only on Java 8 and older, and we don't support these versions anymore.
The prelude file is an obsolete feature that we probably don't need anymore.

* Removed the targets for obtaining tools.jar from the JVM.
* Removed the unescape_filenames macro.
* Removed the prelude file.
* Support for 252-EAP

---------

Co-authored-by: Evgenii Novozhilov <[email protected]>
…er (#7691)

Revert to previous behaviour of using the ScopedProcess Handler in the BlazeCommandGenericRunConfigurationRunner and remove support for the generic process handler.

FYI, the entire logic with BuildResultHelperBep and LocalBuildEventProtocolTestFinderStrategy is pretty messy. The result helper is closed before the strategy is executed, causing all the 'could not delete BEP file' warnings. This needs a proper refactor later.

fixes #7648 #7623
partially revert AOSP changes to
the previous implementation

fixes #7682
This change allows the user to specify a set of flags which
will be applied when a Python debug session is undertaken.

Co-authored-by: Myroslav <[email protected]>
Update the HeaderRootTrimmer to use the standard Path API instead of the VFS. This substantially reduces loads into the VFS. The HeaderRootTrimmer also disallows bazel-bin as a valid header root, since this would create a watch root for the entire bin directory.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⤵️ pull merge-conflict Resolve conflicts manually
Projects
None yet
Development

Successfully merging this pull request may close these issues.