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

fix: silence benchmark output #126

Merged
merged 1 commit into from
Apr 3, 2024
Merged

fix: silence benchmark output #126

merged 1 commit into from
Apr 3, 2024

Conversation

trym-b
Copy link
Contributor

@trym-b trym-b commented Apr 3, 2024

Since commit
d8d316a the
benchmark results of BenchmarkReadFileWithError
are no longer present.
BenchmarkReadFileWithError has not been deleted, and it seems like some of the output printed to
the benchmark result file causes
github-action-benchmark to fail finding this
result.

The reason why commit
d8d316a triggered this error is because it added the required lfs
checkout so that the test-data was cloned
correctly.

As a workaround, this commit silences the output
of the benchmark BenchmarkReadFileWithError.

Since commit
d8d316a the
benchmark results of `BenchmarkReadFileWithError`
are no longer present.
`BenchmarkReadFileWithError` has not been deleted,
and it seems like some of the output printed to
the benchmark result file causes
`github-action-benchmark` to fail finding this
result.

The reason why commit
d8d316a triggered
this error is because it added the required `lfs`
checkout so that the test-data was cloned
correctly.

As a workaround, this commit silences the output
of the benchmark `BenchmarkReadFileWithError`.
@trym-b
Copy link
Contributor Author

trym-b commented Apr 3, 2024

This url points to a benchmark result that contains the missing benchmark as a test in a separate repo: trym-b@45fe0da

@trym-b trym-b merged commit df554c4 into main Apr 3, 2024
8 checks passed
@trym-b trym-b deleted the fix/silence-benchmark-output branch April 3, 2024 14:34
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