cockroachdb / cockroach

CockroachDB — the cloud native, distributed SQL database designed for high availability, effortless scale, and control over data placement.
https://www.cockroachlabs.com
Other
30.15k stars 3.81k forks source link

roachtest: admission-control/multitenant-fairness/read-heavy/skewed failed #131139

Closed cockroach-teamcity closed 1 month ago

cockroach-teamcity commented 2 months ago

roachtest.admission-control/multitenant-fairness/read-heavy/skewed failed with artifacts on master @ 83589fb87caa92fb42e83994f1691978f37e4cbb:

(assertions.go:363).Fail: 
    Error Trace:    github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/admission_control_multitenant_fairness.go:332
                                github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/admission_control_multitenant_fairness.go:103
                                main/pkg/cmd/roachtest/test_runner.go:1285
                                src/runtime/asm_amd64.s:1695
    Error:          Received unexpected error:
                    sql: Scan error on column index 0, name "sum": converting NULL to float64 is unsupported
    Test:           admission-control/multitenant-fairness/read-heavy/skewed
(require.go:1357).NoError: FailNow called
test artifacts and logs in: /artifacts/admission-control/multitenant-fairness/read-heavy/skewed/run_1

Parameters:

See: roachtest README

See: How To Investigate (internal)

See: Grafana

/cc @cockroachdb/storage

This test on roachdash | Improve this report!

Jira issue: CRDB-42399

aadityasondhi commented 1 month ago

sql: Scan error on column index 0, name "sum": converting NULL to float64 is unsupported

Not a release blocker. Failing on a query to crdb_internal.statement_statistics which we use for stats in this test.

aadityasondhi commented 1 month ago

Ran this query locally, I don't see an issue with it. Since this failure only happened once and only one of the subtests of this roachtest, I think we can assume it was a flake and do nothing at the moment.

It could be that the table wasn't fully initialized when we ran the query during the test.