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 BENCHMARK_DIR not used #44

Merged
merged 1 commit into from
Jun 28, 2016
Merged

fix BENCHMARK_DIR not used #44

merged 1 commit into from
Jun 28, 2016

Conversation

norihiro-w
Copy link
Contributor

fix an issue that benchmarking with the user provided BENCHMARK_DIR is not working

@wenqing
Copy link
Member

wenqing commented Jun 24, 2016

👍

@@ -1,4 +1,4 @@
set(BENCHMARK_OUTPUT_DIRECTORY ${PROJECT_BINARY_DIR}/benchmarks/${benchmarkDir})
set(BENCHMARK_OUTPUT_DIRECTORY ${BENCHMARK_DIR}/${benchmarkDir})
Copy link
Member

@bilke bilke Jun 24, 2016

Choose a reason for hiding this comment

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

The intention here is to have benchmark output files just in the build-directory to keep the source dir in a clean state. This is especially helpful in Jenkins to have a build and benchmark run in one enclosed directory.

So I suggest to either revert this change or introduce another variable (e.g. BENCHMARK_OUTPUT_DIR). ✅

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i see. then i will revert this change. is it still ok if I keep the change at line 50?

Copy link
Member

Choose a reason for hiding this comment

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

Sure, go ahead!

@norihiro-w
Copy link
Contributor Author

reverted the change and keep the behavior that benchmark outputs are generated under build directories.

@norihiro-w norihiro-w merged commit 111ff0d into ufz:master Jun 28, 2016
@norihiro-w norihiro-w deleted the fix-bench branch June 28, 2016 04:11
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.

3 participants