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

regenerate config jsons, reduce noise #9644

Closed
wants to merge 2 commits into from

Conversation

likewhatevs
Copy link
Contributor

Differential Revision: D34543778

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D34543778

Copy link
Contributor

@jay-zhuang jay-zhuang left a comment

Choose a reason for hiding this comment

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

LGTM

Comment on lines +219 to +222
for metric in overloaded_metric_list:
if not isinstance(metric, dict):
clean_benchmarks[binary][benchmark].append(metric)
TARGETS.add_fancy_bench_config(config_dict['name'], clean_benchmarks, False, config_dict['expected_runtime_one_iter'], config_dict['sl_iterations'], config_dict['regression_threshold'])
Copy link
Contributor

Choose a reason for hiding this comment

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

maybe the default setting could be added here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it is added upstream of the json

jay-zhuang added a commit to jay-zhuang/rocksdb that referenced this pull request Mar 1, 2022
Better use the released clang-format version instead of the one from dev
branch. Otherwise the format report could be inconsistent with local
development env and CI. e.g.: facebook#9644

Test Plan: CI
facebook-github-bot pushed a commit that referenced this pull request Mar 1, 2022
Summary:
We should use the released clang-format version instead of the one from
dev branch. Otherwise the format report could be inconsistent with local
development env and CI. e.g.: #9644

Pull Request resolved: #9646

Test Plan: CI

Reviewed By: riversand963

Differential Revision: D34554065

Pulled By: jay-zhuang

fbshipit-source-id: b841bc400becb4272be18c803eb03a7a1172da6f
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D34543778

patsomaru and others added 2 commits March 1, 2022 11:34
Summary: Pull Request resolved: facebook#9643

Differential Revision: D34543573

fbshipit-source-id: 4fbe6b31c8e2f1afb68fec9573e9c7bd1a853011
Summary: Pull Request resolved: facebook#9644

Reviewed By: jay-zhuang

Differential Revision: D34543778

fbshipit-source-id: a637bcedb79c63bc7c8c342f6496ec07065c2ed5
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D34543778

tabokie pushed a commit to tabokie/rocksdb that referenced this pull request Mar 8, 2023
…k#9646)

Summary:
We should use the released clang-format version instead of the one from
dev branch. Otherwise the format report could be inconsistent with local
development env and CI. e.g.: facebook#9644

Pull Request resolved: facebook#9646

Test Plan: CI

Reviewed By: riversand963

Differential Revision: D34554065

Pulled By: jay-zhuang

fbshipit-source-id: b841bc400becb4272be18c803eb03a7a1172da6f
tabokie pushed a commit to tabokie/rocksdb that referenced this pull request Mar 8, 2023
…k#9646)

Summary:
We should use the released clang-format version instead of the one from
dev branch. Otherwise the format report could be inconsistent with local
development env and CI. e.g.: facebook#9644

Pull Request resolved: facebook#9646

Test Plan: CI

Reviewed By: riversand963

Differential Revision: D34554065

Pulled By: jay-zhuang

fbshipit-source-id: b841bc400becb4272be18c803eb03a7a1172da6f
Signed-off-by: tabokie <xy.tao@outlook.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants