Skip to content

Presubmit engine builds not uploading properly to flutter_archives_v2 GCS bucket #149780

Closed

Description

@eyebrowsoffire

It appears that presubmit builds are no longer uploading to a stable location in GCS, therefore making the instructions https://github.com/flutter/flutter/blob/master/docs/engine/Testing-presubmit-Engine-PRs-with-the-Flutter-framework.md invalid. The GCS bucket seems to namespace the artifacts by build bucket ID now. We suspect this started with this change: https://flutter-review.googlesource.com/c/recipes/+/57140

Activity

  1. christopherfujino commented on Jun 5, 2024

    @christopherfujino
    Contributor

    For reference, see this engine try build that uploaded artifacts: https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20Engine%20Drone/2389413/infra

  2. added
    in triagePresently being triaged by the triage team
    team-infraOwned by Infrastructure team
    and removed
    in triagePresently being triaged by the triage team
    on Jun 6, 2024
  3. zanderso commented on Jun 6, 2024

    @zanderso
    Member

    The breakage is due to the recipe change here, which was a partial migration to a new way of uploading the artifacts from presubmit.

    I believe that commit (and two follow-on fixes here and here) can be safely backed out to restore the previous behavior. There's some risk that there were also compensating changes in the monorepo recipes that would also have to be reverted, as well, but I'm less familiar. @aam may remember.

  4. christopherfujino commented on Jun 6, 2024

    @christopherfujino
    Contributor
  5. eyebrowsoffire commented on Jul 2, 2024

    @eyebrowsoffire
    ContributorAuthor
  6. github-actions commented on Jul 16, 2024

    @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.

  7. locked as resolved and limited conversation to collaborators on Jul 16, 2024
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

    team-infraOwned by Infrastructure team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions