You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our benchmark files currently have no way to print the return the possible options to the user. If we'd implement such feature, we would not have to worry about our benchmark tests anymore that they might fail due to changes in any benchmark options. We could just go ahead and read the benchmarks specific options first and then run the test with the specific subset of options that are suitable.
I opened this issue as a kind of feature request in case someone else would like to open a PR to implement this and also to get feedback from others about it.
// cc @Trott I guess you might be interested in something like this.
The text was updated successfully, but these errors were encountered:
This adds a new `test` option. Using it automatically uses a single
minimal option matrix to verify the benchmark works as expected.
Using the new `all` option makes sure all test suites are run.
On top of that the benchmarks will from now on report properly
what category might have a typo, if any.
The http duration was also refactored to use a option instead of
relying on a configuration setting.
The fixture folder is ignored as test suite from now on.
PR-URL: #31396Fixes: #31083
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Our benchmark files currently have no way to print the return the possible options to the user. If we'd implement such feature, we would not have to worry about our benchmark tests anymore that they might fail due to changes in any benchmark options. We could just go ahead and read the benchmarks specific options first and then run the test with the specific subset of options that are suitable.
I opened this issue as a kind of feature request in case someone else would like to open a PR to implement this and also to get feedback from others about it.
// cc @Trott I guess you might be interested in something like this.
The text was updated successfully, but these errors were encountered: