Skip to content

sql/opt/exec/explain: TestMaximumMemoryUsage failed #146052

@cockroach-teamcity

Description

@cockroach-teamcity

sql/opt/exec/explain.TestMaximumMemoryUsage failed on release-24.1 @ dd6fcacea1091baf9e9361bf65bb8462f736f8f4:

=== RUN   TestMaximumMemoryUsage
    test_log_scope.go:165: test logs captured to: outputs.zip/logTestMaximumMemoryUsage2060469103
    test_log_scope.go:76: use -show-logs to present logs inline
    test_server_shim.go:152: automatically injected an external process virtual cluster under test; see comment at top of test_server_shim.go for details.
    output_test.go:426: condition failed to evaluate within 45s: from output_test.go:444: expected maximum memory usage to be at least 5 MiB, full output:
        planning time: 196µs
        execution time: 7.6s
        distribution: full
        vectorized: true
        plan type: generic, reused
        rows decoded from KV: 10,000 (9.9 MiB, 10,000 gRPC calls)
        cumulative time spent in KV: 14.8s
        maximum memory usage: 0 B
        network usage: 4.5 KiB (6 messages)
        sql cpu time: 39ms
        estimated RUs consumed: 0
        isolation level: serializable
        priority: normal
        quality of service: regular
        • group (hash)
        │ group by: bucket
        │
        └── • scan
              nodes: n2, n3
              actual row count: 10,000
              KV time: 14.8s
              KV contention time: 0µs
              KV rows decoded: 10,000
              KV bytes read: 9.9 MiB
              KV gRPC calls: 10,000
              estimated max memory allocated: 4.0 MiB
              sql cpu time: 24ms
              missing stats
              table: t@t_pkey
              spans: FULL SCAN
    panic.go:626: -- test log scope end --
test logs left over in: outputs.zip/logTestMaximumMemoryUsage2060469103
--- FAIL: TestMaximumMemoryUsage (61.18s)

Parameters:

  • attempt=1
  • run=3
  • shard=1
Help

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

This test on roachdash | Improve this report!

Jira issue: CRDB-50359

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions