[pull] androidx-main from androidx:androidx-main#373
Merged
pull[bot] merged 11 commits intowarting:androidx-mainfrom Aug 11, 2025
Merged
[pull] androidx-main from androidx:androidx-main#373pull[bot] merged 11 commits intowarting:androidx-mainfrom
pull[bot] merged 11 commits intowarting:androidx-mainfrom
Conversation
… postsubmit builds The BuildCache interface does not support using Providers to set the `push` value. In light of this, I've created an env var that abstracts the previous logic of setting `push` and set it in our busytown script. The result of this is that configuration cache won't be invalidated due to BUILD_NUMBER changing when setting `push` (config cache is still invalidated but due to other issues) BUG: 434944647 TESTED: ran IS_POSTSUBMIT=true ./gradlew tasks and saw that the uploaded build scan set remote push to true. set the var to false and the expected value was also set Change-Id: Ie6c6bed64ee4426dacacec5320716179fe9da662
Furthermore, fixed a parceling issue in AnnotationResult because of which failures were not getting parceled. Test: All gradle tests passed. Bug: 437310140 Change-Id: Idfd830e21b22f7df324d4b398d792f4a7aa024ca
Updates the onCameraIdsUpdated method to calculate which camera IDs have been removed. It then explicitly removes the corresponding Camera2CameraInfoImpl objects from the mCameraInfos cache. Bug: 436726722 Test: Camera2CameraFactoryTest Change-Id: I7fbe1f79caf364ece5965017f2b541d5d503dfe1
…ce IDs." This reverts commit 37fd8e7. Reason for revert: Causing a NPE in a test Bug: b/436123966 Change-Id: If48d6bceb1f242d8a2212223ad7656b7130ffbb2
…nt device IDs."" into androidx-main
Add quirk GLProcessingStuckOnCodecFlushQuirk and enable stop codec as flush workaround in EncoderImpl. Bug: 391508996 Test: ./gradlew camera:camera-video:connectedAndroidTest Change-Id: I0e110a36e7fc809cbd88c0a67f958fd1065ae508
The previous method invalidated the configuration cache when the `BUILD_NUMBER` environment variable changed (so did other things - see child change) This change defers reading the `BUILD_NUMBER` until the `buildFinished` lifecycle event. By using a `Provider` for the environment variable and setting the build scan values at the end of the build, we ensure the configuration cache is not invalidated. BUG: 435234265 Change-Id: I4a61d746eeabadcee35c88ea3ed7586f0ca86716
* changes: Set BUILD_NUMBER in config cache safe way in build scan config Use env var for remote cache push whose value does not change between postsubmit builds
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.3)
Can you help keep this open source service alive? 💖 Please sponsor : )