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 costfuzz log on error while running perturbed statement #81102

Merged
merged 1 commit into from
May 7, 2022

Conversation

michae2
Copy link
Collaborator

@michae2 michae2 commented May 6, 2022

Also log the unperturbed statement when the costfuzz test encounters an
error executing the perturbed statement.

This can be fixed by hand, but it's easier if the costfuzz log is
correct.

Informs: #81032

Release note: None

Also log the unperturbed statement when the costfuzz test encounters an
error executing the perturbed statement.

This can be fixed by hand, but it's easier if the costfuzz log is
correct.

Informs: cockroachdb#81032

Release note: None
@michae2 michae2 requested review from msirek and a team May 6, 2022 19:04
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Collaborator

@rytaft rytaft left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @msirek)

@michae2
Copy link
Collaborator Author

michae2 commented May 6, 2022

TFTR!

bors r=rytaft

Copy link
Contributor

@msirek msirek 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! 1 of 0 LGTMs obtained (waiting on @michae2)


pkg/cmd/roachtest/tests/costfuzz.go line 226 at r1 (raw file):

	rows2, err := conn.Query(stmt)
	if err != nil {
		logStmt(stmt)

Does calling this function twice cause different behavior on the 2nd call? It's also called below.

@craig
Copy link
Contributor

craig bot commented May 6, 2022

Build failed (retrying...):

Copy link
Collaborator Author

@michae2 michae2 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! 1 of 0 LGTMs obtained (waiting on @msirek)


pkg/cmd/roachtest/tests/costfuzz.go line 226 at r1 (raw file):

Previously, msirek (Mark Sirek) wrote…

Does calling this function twice cause different behavior on the 2nd call? It's also called below.

Calling this function twice simply logs the statement twice. (The log is supposed to be a record of statements executed during this run. We executed this statement twice, once normally and once after setting the perturbation seed, so we need the log to reflect that for reproducibility.)

Copy link
Contributor

@msirek msirek 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! 1 of 0 LGTMs obtained (waiting on @michae2)


pkg/cmd/roachtest/tests/costfuzz.go line 226 at r1 (raw file):

Previously, michae2 (Michael Erickson) wrote…

Calling this function twice simply logs the statement twice. (The log is supposed to be a record of statements executed during this run. We executed this statement twice, once normally and once after setting the perturbation seed, so we need the log to reflect that for reproducibility.)

Right, of course. Thanks!

@craig
Copy link
Contributor

craig bot commented May 7, 2022

Build succeeded:

@craig craig bot merged commit e04373b into cockroachdb:master May 7, 2022
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.

4 participants