Skip to content
Validate Android

Fix display: contents nodes not being cloned with the wrong owner #2752

Sign in to view logs

Fix display: contents nodes not being cloned with the wrong owner

Fix display: contents nodes not being cloned with the wrong owner #2752

Triggered via pull request July 10, 2025 12:23
@j-piaseckij-piasecki
synchronize #1826
j-piasecki:@jpiasecki/contents-fix-updates
Status Success
Total duration 4m 22s
Artifacts –

validate-android.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Build [ubuntu-latest][Debug]
Failed to restore v8-gradle|Linux|validate android-build[25eb1ba18f52793d8a9683daf4dddeb6]-ff8eea87dcc21ba58ac79af1ac23f765027bc945: Error: Cache service responded with 400
Build [ubuntu-latest][Release]
Failed to restore v8-gradle|Linux|validate android-build[d59c4dfa72a9aa225c90a7ec4feaf459]-ff8eea87dcc21ba58ac79af1ac23f765027bc945: Error: Cache service responded with 400
Build [windows-latest][Debug]
Failed to restore v8-gradle|Windows|validate android-build[f1e80aac4a120218d9b8a2ea10a2637e]-ff8eea87dcc21ba58ac79af1ac23f765027bc945: Error: Cache service responded with 400
Build [windows-latest][Release]
Failed to restore v8-gradle|Windows|validate android-build[8bac7a31a4f2454ea922597b599b138e]-ff8eea87dcc21ba58ac79af1ac23f765027bc945: Error: Cache service responded with 400