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

Make benchmark_effect_size test less flaky #195

Merged
merged 1 commit into from
Aug 8, 2022

Conversation

fitzgen
Copy link
Member

@fitzgen fitzgen commented Aug 8, 2022

It complains if there isn't any variance between samples, so bump up the number
of iterations we perform to make getting all identical samples extremely
unlikely.

This flaky test seems to be holding back #194 and #193

It complains if there isn't any variance between samples, so bump up the number
of iterations we perform to make getting all identical samples extremely
unlikely.
@fitzgen fitzgen requested a review from abrown August 8, 2022 20:54
@abrown
Copy link
Collaborator

abrown commented Aug 8, 2022

Wait... how did you figure out that variance is the issue with this test? When I look at the test output, I don't see that, e.g., with this latest failure. I guessed that it was some weird file issue in #178 but if it's actually fixed by more runs, then great! But how? Shouldn't we be able to see something of this in the test output?

@fitzgen
Copy link
Member Author

fitzgen commented Aug 8, 2022

I think the crate we use has some internal unwraps/panics rather than exposing results.

But I did see at least one bit of log output for one of the failures (maybe before doing a retry?) that mentioned variance.

Copy link
Collaborator

@abrown abrown left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, let's see if this works!

@abrown abrown merged commit c32d409 into bytecodealliance:main Aug 8, 2022
@fitzgen fitzgen deleted the make-test-less-flaky-in-ci branch August 8, 2022 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants