Skip to content

Update run_verify_binaries_codesigned_tests to collect and print all the missing/unexpected binaries on failure, instead of failing-fast on the first #154029

@jmagman

Description

@jmagman

This was an issue in #153787.

@itsjustkevin asks

Is it possible that the test failed only on the first binary?

I think so, based on more binaries missing from the list: #154027

The test should be updated to collect all the unexpected binaries, and print them all:

for (final String binaryPath in binaryPaths)
if (allExpectedFiles.contains(binaryPath)) binaryPath
else throw Exception('Found unexpected binary in cache: $binaryPath'),

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listinfra: releaseRelease-related requests and toolingteam-infraOwned by Infrastructure teamtriaged-infraTriaged by Infrastructure team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions