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

pkg/sql/logictest/tests/fakedist-vec-off/fakedist-vec-off_test: TestLogic_inverted_filter_geospatial failed #95359

Closed
cockroach-teamcity opened this issue Jan 17, 2023 · 3 comments · Fixed by #95406
Assignees
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. T-sql-queries SQL Queries Team
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Jan 17, 2023

pkg/sql/logictest/tests/fakedist-vec-off/fakedist-vec-off_test.TestLogic_inverted_filter_geospatial failed with artifacts on master @ 6116ab435ee2cc37af34c99e28dec51b6cfa0eb4:

=== RUN   TestLogic_inverted_filter_geospatial
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/8ee417166775d051de542acde5a083e2/logTestLogic_inverted_filter_geospatial2229431385
    test_log_scope.go:79: use -show-logs to present logs inline
    logic.go:3233: 
        
        /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/9502/execroot/com_github_cockroachdb_cockroach/bazel-out/aarch64-fastbuild/bin/pkg/sql/logictest/tests/fakedist-vec-off/fakedist-vec-off_test_/fakedist-vec-off_test.runfiles/com_github_cockroachdb_cockroach/pkg/sql/logictest/testdata/logic_test/inverted_filter_geospatial:52: SELECT k FROM geo_table WHERE 'POINT(3.0 3.0)'::geometry && geom ORDER BY k
        expected success, but found
        (0A000) this box2d comparison operator is experimental
        settings.go:33: in checkExperimentalBox2DComparisonOperatorEnabled()
    logic.go:2907: 
         pq: this box2d comparison operator is experimental
[15:11:13] --- done: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/9502/execroot/com_github_cockroachdb_cockroach/bazel-out/aarch64-fastbuild/bin/pkg/sql/logictest/tests/fakedist-vec-off/fakedist-vec-off_test_/fakedist-vec-off_test.runfiles/com_github_cockroachdb_cockroach/pkg/sql/logictest/testdata/logic_test/inverted_filter_geospatial with config fakedist-vec-off: 9 tests, 2 failures
    logic.go:4025: 
        /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/9502/execroot/com_github_cockroachdb_cockroach/bazel-out/aarch64-fastbuild/bin/pkg/sql/logictest/tests/fakedist-vec-off/fakedist-vec-off_test_/fakedist-vec-off_test.runfiles/com_github_cockroachdb_cockroach/pkg/sql/logictest/testdata/logic_test/inverted_filter_geospatial:58: error while processing
    logic.go:4025: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/9502/execroot/com_github_cockroachdb_cockroach/bazel-out/aarch64-fastbuild/bin/pkg/sql/logictest/tests/fakedist-vec-off/fakedist-vec-off_test_/fakedist-vec-off_test.runfiles/com_github_cockroachdb_cockroach/pkg/sql/logictest/testdata/logic_test/inverted_filter_geospatial:58: too many errors encountered, skipping the rest of the input
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/8ee417166775d051de542acde5a083e2/logTestLogic_inverted_filter_geospatial2229431385
--- FAIL: TestLogic_inverted_filter_geospatial (1.37s)
Help

See also: How To Investigate a Go Test Failure (internal)

/cc @cockroachdb/sql-queries

This test on roachdash | Improve this report!

Jira issue: CRDB-23480

@cockroach-teamcity cockroach-teamcity added branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. labels Jan 17, 2023
@cockroach-teamcity cockroach-teamcity added this to the 23.1 milestone Jan 17, 2023
@blathers-crl blathers-crl bot added the T-sql-queries SQL Queries Team label Jan 17, 2023
@cucaroach
Copy link
Contributor

This doesn't repro, looks like a setting flake as the test sets the setting right before this test but apparently it was set or was reset somehow.

@renatolabs
Copy link
Contributor

This does seem to reproduce fairly easily under stress. I did a quick bisection and it seems to point to #93377 as the PR that introduced the failure (specifically, 5a5f339).

@cucaroach
Copy link
Contributor

@yuzefovich explained that in a distsql situation the cluster setting is asynchronously set on other nodes and this query should have a retry clause.

craig bot pushed a commit that referenced this issue Jan 18, 2023
95248: streamingest: add a replication lag metric r=lidorcarmel a=lidorcarmel

Add a metric to track the lag of the replication frontier, in seconds.

Informs: #92959

Epic: CRDB-18752

Release note: None

95406: sql: retry query requiring cluster setting propagation r=cucaroach a=cucaroach

Fixes: #95359
Release note: None
Epic: none


95453: changefeedccl: nilsafe kafkaSink.Close r=[miretskiy] a=HonoreDB

We were tolerating nils in other parts of Close, but not here, which can create a race condition if a sink gets closed before being fully initialized resulting in a panic.

Fixes #95278
Release note: None

Co-authored-by: Lidor Carmel <[email protected]>
Co-authored-by: Tommy Reilly <[email protected]>
Co-authored-by: Aaron Zinger <[email protected]>
@craig craig bot closed this as completed in 9e5bca6 Jan 18, 2023
blathers-crl bot pushed a commit that referenced this issue Jan 18, 2023
cucaroach added a commit that referenced this issue Jan 19, 2023
@mgartner mgartner moved this to Done in SQL Queries Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. T-sql-queries SQL Queries Team
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants