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

roachtest: fix tpchvec perf #48107

Merged
merged 1 commit into from
Apr 28, 2020
Merged

roachtest: fix tpchvec perf #48107

merged 1 commit into from
Apr 28, 2020

Conversation

yuzefovich
Copy link
Member

@yuzefovich yuzefovich commented Apr 28, 2020

This commit fixes a problem with "test case struct" resolution that was
introduced recently when we added smithcmp config to tpchvec test.
The root of the issue is that testRun function was made a part of the
tpchVecTestCase interface which doesn't really makes sense.

Release note: None

@yuzefovich yuzefovich requested a review from asubiotto April 28, 2020 14:24
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@yuzefovich
Copy link
Member Author

See #47401 (comment)

Copy link
Contributor

@asubiotto asubiotto left a comment

Choose a reason for hiding this comment

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

Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (waiting on @asubiotto and @yuzefovich)


pkg/cmd/roachtest/tpchvec.go, line 140 at r1 (raw file):

	c *cluster,
	version crdbVersion,
	vectorizeOptions []bool,

I think this solution is confusing because we have the option to either use the passed in variable or call b.vectorizeOptions and the other testRun implementation ignores the arguments. The problem here is that there are no commonalities between the test types so putting this into an interface doesn't work cleanly. Instead, I think we should get rid of testRun and pass in a function to runTPCHVec one of which is the original and the other which is the new placeholder test.

This commit fixes a problem with "test case struct" resolution that was
introduced recently when we added `smithcmp` config to `tpchvec` test.
The root of the issue is that `testRun` function was made a part of the
`tpchVecTestCase` interface which doesn't really makes sense.

Release note: None
Copy link
Member Author

@yuzefovich yuzefovich left a comment

Choose a reason for hiding this comment

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

Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (waiting on @asubiotto)


pkg/cmd/roachtest/tpchvec.go, line 140 at r1 (raw file):

Previously, asubiotto (Alfonso Subiotto Marqués) wrote…

I think this solution is confusing because we have the option to either use the passed in variable or call b.vectorizeOptions and the other testRun implementation ignores the arguments. The problem here is that there are no commonalities between the test types so putting this into an interface doesn't work cleanly. Instead, I think we should get rid of testRun and pass in a function to runTPCHVec one of which is the original and the other which is the new placeholder test.

Good point, done.

Copy link
Contributor

@asubiotto asubiotto left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained

@yuzefovich
Copy link
Member Author

TFTR!

bors r+

@yuzefovich
Copy link
Member Author

bors r+

@craig
Copy link
Contributor

craig bot commented Apr 28, 2020

Build succeeded

@craig craig bot merged commit c2668dc into cockroachdb:master Apr 28, 2020
@yuzefovich yuzefovich deleted the tpchvec branch April 28, 2020 23:17
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