Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: separate out tests with byte differences in the report #459

Merged
merged 1 commit into from
Aug 12, 2024

Conversation

dlockhart
Copy link
Member

When Chrome makes a new release, it can sometimes result in a lot of failed tests due to byte differences. Since these are technically failures (that we're OK with), these get mixed in with potential real failures, which makes reviewing them tedious as you need to scroll through all the failed tests scanning for a legitimate failure.

This change breaks out the "byte diff" failures from the "real" failures in the report, so you can easily filter down to just the real failures and ignore the byte diff ones.

Screenshot 2024-08-09 at 4 22 49 PM

@dlockhart dlockhart requested a review from a team as a code owner August 9, 2024 20:24
@dlockhart dlockhart requested a review from bearfriend August 9, 2024 20:25
@dlockhart dlockhart force-pushed the dlockhart/report-byte-diff branch from d68d774 to 4f7d665 Compare August 9, 2024 20:34
@dlockhart dlockhart merged commit 38bc491 into main Aug 12, 2024
3 checks passed
@dlockhart dlockhart deleted the dlockhart/report-byte-diff branch August 12, 2024 13:14
Copy link

🎉 This PR is included in version 1.21.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants