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: follower-reads/nodes=3 failed #52615

Closed
cockroach-teamcity opened this issue Aug 11, 2020 · 2 comments · Fixed by #52925
Closed

roachtest: follower-reads/nodes=3 failed #52615

cockroach-teamcity opened this issue Aug 11, 2020 · 2 comments · Fixed by #52925
Labels
C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
Milestone

Comments

@cockroach-teamcity
Copy link
Member

(roachtest).follower-reads/nodes=3 failed on release-20.1@7cd827ca05400a1b27adedfe577c051c114fcde7:

The test failed on branch=release-20.1, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/follower-reads/nodes=3/run_1
	follower_reads.go:196,test_runner.go:754: error verifying node values: pq: AS OF SYSTEM TIME: only constant expressions or experimental_follower_read_timestamp are allowed

More

Artifacts: /follower-reads/nodes=3
Related:

See this test on roachdash
powered by pkg/cmd/internal/issues

@cockroach-teamcity cockroach-teamcity added branch-release-20.1 C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. labels Aug 11, 2020
@cockroach-teamcity cockroach-teamcity added this to the 20.2 milestone Aug 11, 2020
@cockroach-teamcity
Copy link
Member Author

(roachtest).follower-reads/nodes=3 failed on release-20.1@607d3fb91a15fbd4613f22396d5828c4d27d390b:

The test failed on branch=release-20.1, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/follower-reads/nodes=3/run_1
	follower_reads.go:196,test_runner.go:754: error verifying node values: pq: AS OF SYSTEM TIME: only constant expressions or experimental_follower_read_timestamp are allowed

More

Artifacts: /follower-reads/nodes=3
Related:

See this test on roachdash
powered by pkg/cmd/internal/issues

@cockroach-teamcity
Copy link
Member Author

(roachtest).follower-reads/nodes=3 failed on release-20.1@8352fd645f4517ab0650ad637e22b20d9e524d53:

The test failed on branch=release-20.1, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/follower-reads/nodes=3/run_1
	follower_reads.go:196,test_runner.go:754: error verifying node values: pq: AS OF SYSTEM TIME: only constant expressions or experimental_follower_read_timestamp are allowed

More

Artifacts: /follower-reads/nodes=3
Related:

See this test on roachdash
powered by pkg/cmd/internal/issues

craig bot pushed a commit that referenced this issue Aug 18, 2020
52925: roachtest: continue using experimental_follower_read_timestamp() builtin r=nvanbenschoten a=nvanbenschoten

Fixes #52612.
Fixes #52614.
Fixes #52615.
Fixes #52876.

In 7284376, we removed the "experimental_" prefix from the
`experimental_follower_read_timestamp()` builtin. This accidentally
broke the `follower-reads/nodes=3` roachtest on everything but `master`.
To maintain backwards compatibility, continue using the old form of the
builtin in roachtests.

Co-authored-by: Nathan VanBenschoten <[email protected]>
@craig craig bot closed this as completed in 6a071ce Aug 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant