Add more explicit logging (just to stderr
) if a try-job detects an untriaged image
#51454
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Work towards flutter/flutter#145219.
Previously all logging would be silent in the case that
test_foo
uploads a digest that is considered "untriaged", and we'd be entirely reliant on theflutter-gold
check to pick this up asynchronously.As part of debugging flutter/flutter#145219 (but probably to keep this code indefinitely, it's not harmful), we now unconditionally log the swallowed failures to
stderr
so they will show up in our LUCI logs./cc @gaaclarke @jonahwilliams