Skip to content

Workaround for ScalaMeter incorrect report path #1218

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

Merged
merged 2 commits into from
Apr 18, 2016

Conversation

liufengyun
Copy link
Contributor

The ScalaMeter issue is reported here:

https://github.com/scalameter/scalameter/pull/163/files

The issue exists both in v0.7 and v0.6. As dotty uses v0.6 now,
use this workaround until we upgrate to a new version of ScalaMeter.

With this PR, we no longer need to maintain two separate folders for reports.

Please review @DarkDimius .

The ScalaMeter issue is reported here:

https://github.com/scalameter/scalameter/pull/163/files

The issue exists both in v0.7 and v0.6. As dotty uses v0.6 now,
use this workaround until we upgrate to a new version of ScalaMeter.
@liufengyun liufengyun mentioned this pull request Apr 14, 2016
7 tasks
@@ -239,7 +239,6 @@ object DottyBuild extends Build {

libraryDependencies ++= Seq("com.storm-enroute" %% "scalameter" % "0.6" % Test,
"com.novocode" % "junit-interface" % "0.11"),
testFrameworks += new TestFramework("org.scalameter.ScalaMeterFramework"),
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 removed this, because we never run dotty-bench/test, we use dotty-bench/test:run. The latter doesn't require the framework integration.

@DarkDimius
Copy link
Contributor

LGTM

@DarkDimius DarkDimius merged commit 16b90f7 into scala:master Apr 18, 2016
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