Skip to content

Slimpeller needs to use different paths for ci/android_release_slimpeller_arm64 #168180

@jtmcdole

Description

@jtmcdole

ci/android_release_slimpeller_arm64 maps to the same GCS paths as android-arm64-release and thus can step on binary outputs of other builders.

"base_path": "out/ci/android_release_slimpeller_arm64/zip_archives/",
"include_paths": [
"out/ci/android_release_slimpeller_arm64/zip_archives/android-arm64-release/artifacts.zip",
"out/ci/android_release_slimpeller_arm64/zip_archives/android-arm64-release/linux-x64.zip",
"out/ci/android_release_slimpeller_arm64/zip_archives/android-arm64-release/symbols.zip",
"out/ci/android_release_slimpeller_arm64/zip_archives/android-arm64-release/analyze-snapshot-linux-x64.zip",
"out/ci/android_release_slimpeller_arm64/zip_archives/download.flutter.io"
],

Mitigating by removing the config in #168178

See this comment for suggested fix: #168178 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listslimpellerEngine binary size reduction. go/slimpellerteam-engineOwned by Engine teamtriaged-engineTriaged by Engine team

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions