Skip to content

android tests are all red #173143

Closed
#173169
Closed
android tests are all red#173143
#173169
Labels
P0Critical issues such as a build break or regressionteam-engineOwned by Engine team

Description

@gaaclarke
gaaclarke
opened on Aug 1, 2025
Image

Allegedly introduced in #173135 but that isn't possible.

codefu believes it's hashing releated.

examples

log

[2025-08-01 16:27:33.193772] [STDOUT] stderr: [        ] Caused by: org.gradle.api.internal.artifacts.ivyservice.TypedResolveException: Could not resolve all files for configuration ':app:profileRuntimeClasspath'.
[2025-08-01 16:27:33.193777] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.artifacts.ResolveExceptionMapper.mapFailures(ResolveExceptionMapper.java:56)
[2025-08-01 16:27:33.193783] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration$DefaultResolutionHost.consolidateFailures(DefaultConfiguration.java:1974)
[2025-08-01 16:27:33.193788] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.artifacts.configurations.ResolutionHost.rethrowFailuresAndReportProblems(ResolutionHost.java:75)
[2025-08-01 16:27:33.193795] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.artifacts.configurations.ResolutionBackedFileCollection.maybeThrowResolutionFailures(ResolutionBackedFileCollection.java:86)
[2025-08-01 16:27:33.193800] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.artifacts.configurations.ResolutionBackedFileCollection.visitContents(ResolutionBackedFileCollection.java:76)
[2025-08-01 16:27:33.193806] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.file.AbstractFileCollection.visitStructure(AbstractFileCollection.java:360)
[2025-08-01 16:27:33.193811] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.file.CompositeFileCollection.lambda$visitContents$0(CompositeFileCollection.java:113)
[2025-08-01 16:27:33.193816] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.file.collections.UnpackingVisitor.add(UnpackingVisitor.java:67)
[2025-08-01 16:27:33.193820] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.file.collections.UnpackingVisitor.add(UnpackingVisitor.java:92)
[2025-08-01 16:27:33.193828] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.file.DefaultFileCollectionFactory$ResolvingFileCollection.visitChildren(DefaultFileCollectionFactory.java:306)
[2025-08-01 16:27:33.193833] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.file.CompositeFileCollection.visitContents(CompositeFileCollection.java:113)
[2025-08-01 16:27:33.193838] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.file.AbstractFileCollection.visitStructure(AbstractFileCollection.java:360)
[2025-08-01 16:27:33.196747] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.file.CompositeFileCollection.lambda$visitContents$0(CompositeFileCollection.java:113)
[2025-08-01 16:27:33.196788] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.tasks.PropertyFileCollection.visitChildren(PropertyFileCollection.java:48)
[2025-08-01 16:27:33.196796] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.file.CompositeFileCollection.visitContents(CompositeFileCollection.java:113)
[2025-08-01 16:27:33.196802] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.file.AbstractFileCollection.visitStructure(AbstractFileCollection.java:360)

[2025-08-01 16:26:24.353122] [STDOUT] stderr: [        ] Cause 36: org.gradle.internal.locking.LockOutOfDateException: Did not resolve 'androidx.core:core-ktx:1.13.1' which is part of the dependency lock state
[2025-08-01 16:26:24.353127] [STDOUT] stderr: [        ] 	at org.gradle.internal.locking.DependencyLockingGraphVisitor.createLockingFailures(DependencyLockingGraphVisitor.java:153)
[2025-08-01 16:26:24.353166] [STDOUT] stderr: [        ] 	at org.gradle.internal.locking.DependencyLockingGraphVisitor.collectLockingFailures(DependencyLockingGraphVisitor.java:143)
[2025-08-01 16:26:24.353188] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.artifacts.ivyservice.DefaultConfigurationResolver.resolveGraph(DefaultConfigurationResolver.java:290)
[2025-08-01 16:26:24.353213] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.artifacts.ivyservice.ShortCircuitEmptyConfigurationResolver.resolveGraph(ShortCircuitEmptyConfigurationResolver.java:82)
[2025-08-01 16:26:24.353274] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration$1.call(DefaultConfiguration.java:785)
[2025-08-01 16:26:24.353314] [STDOUT] stderr: [        ] 	at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration$1.call(DefaultConfiguration.java:777)

Activity

  1. gaaclarke
    added
    P0Critical issues such as a build break or regression
    team-engineOwned by Engine team
    on Aug 1, 2025

  2. gaaclarke commented on Aug 1, 2025

    @gaaclarke
    gaaclarke
    on Aug 1, 2025
    MemberAuthor

    codefu believes this is from #173114

  3. jtmcdole commented on Aug 1, 2025

    @jtmcdole
    jtmcdole
    on Aug 1, 2025
    Member

    It's #173114 or something that does not agree with it in the system.

    Let's try to re-create...

    • git fetch --all
    • checkout master~
    • create branch gh-readonly-queue/master/pr-173135-af88a4f76d9088b5ca9f07d3764e06cd1487b79e
    • cherry pick master (so it looks like the PR in the queue)
    ❯ ./bin/internal/content_aware_hash.sh
4b6f7b0f9849efaa59f515c8e95f3f27a6eb2ffb
❯ git ls-tree --format "%(objectname) %(path)" HEAD -- DEPS engine bin/internal/release-candidate-branch.version | git hash-object --stdin
4b6f7b0f9849efaa59f515c8e95f3f27a6eb2ffb

    So I'll dig in on Monday.

  4. jtmcdole commented on Aug 1, 2025

    @jtmcdole
    jtmcdole
    on Aug 1, 2025
    Member

    It could be something with the way #172378 calls to get the content hash from engine/src/flutter/tools/gn. The gh-readonly-queue/master/pr-173135-af88a4f76d9088b5ca9f07d3764e06cd1487b79e is special, but it has the base right in the name: af88a4f (which was HEAD~).

  5. gaaclarke commented on Aug 2, 2025

    @gaaclarke
    gaaclarke
    on Aug 2, 2025
    MemberAuthor

    The revert hasn't cleared out the red bots unfortunately.

  6. jtmcdole
    closed this as completedon Aug 2, 2025

  7. jtmcdole commented on Aug 2, 2025

    @jtmcdole
    jtmcdole
    on Aug 2, 2025
    Member

    It has now. It needed a kick.

  8. github-merge-queue
    added a commit that references this issue on Aug 4, 2025

    fix: get content hash for master on local engine branches (third atte…

    7da78cb
  9. danilozhang
    added a commit that references this issue on Aug 6, 2025

    fix: get content hash for master on local engine branches (third atte…

    cf709e9
  10. SydneyBao
    added a commit that references this issue on Aug 6, 2025

    fix: get content hash for master on local engine branches (third atte…

    2fbc9c9

  11. github-actions commented on Aug 16, 2025

    @github-actions
    github-actionsbot
    on Aug 16, 2025 – with GitHub Actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  12. github-actions
    locked as resolved and limited conversation to collaborators on Aug 16, 2025
  13. ksokolovskyi
    added a commit that references this issue on Aug 19, 2025

    fix: get content hash for master on local engine branches (third atte…

    4629e3c
  14. mboetger
    added a commit that references this issue on Sep 18, 2025

    fix: get content hash for master on local engine branches (third atte…

    fd14607
  15. korca0220
    added a commit that references this issue on Sep 22, 2025

    fix: get content hash for master on local engine branches (third atte…

    ae73f60
  16. lucaantonelli
    added a commit that references this issue on Nov 21, 2025

    fix: get content hash for master on local engine branches (third atte…

    c3483c1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P0Critical issues such as a build break or regressionteam-engineOwned by Engine team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions