cockroachdb / cockroachdb/cockroach

basalt-26.3: sql/auditlogging: TestReducedAuditConfig failed

Open
#174,875 2 comments 0 reactions 0 assignees View on GitHub
branch-basalt-26.3 C-test-failure O-robot release-blocker T-observability
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

sql/auditlogging.TestReducedAuditConfig [failed](https://mesolite.cluster.engflow.com/invocations/default/d239d62a-5965-4976-9f91-d90c819f20c9?testReportRun=3&testReportShard=1&testReportAttempt=1#targets-Ly9wa2cvc3FsL2F1ZGl0bG9nZ2luZzphdWRpdGxvZ2dpbmdfdGVzdA==) on basalt-26.3 @ [017b84cd0101b832a6ee0c1934d073d108d0b24a](https://github.com/cockroachdb/cockroach/commits/017b84cd0101b832a6ee0c1934d073d108d0b24a):

```
=== RUN TestReducedAuditConfig
test_log_scope.go:172: test logs captured to: outputs.zip/logTestReducedAuditConfig1171510146
test_server_shim.go:168: automatically injected a shared process virtual cluster under test; see comment at top of test_server_shim.go for details.
audit_logging_test.go:373: unexpected number of entries; expected: 1 found: 2
panic.go:694: -- test log scope end --
test logs left over in: outputs.zip/logTestReducedAuditConfig1171510146
--- FAIL: TestReducedAuditConfig (122.08s)
```

Parameters:
- attempt=1
- race=true
- run=3
- shard=1
Help

See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)

/cc @cockroachlabs/obs-prs

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestReducedAuditConfig.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Jira issue: CRDB-68060

Contributor guide

Open the contributing guide

Research direction

Start with sql/auditlogging/audit_logging_test.go at the failing TestReducedAuditConfig assertion around line 373, then inspect the captured test logs linked in the report. Reproduce the failure with the test's race-enabled configuration and determine why two entries appear instead of one. Done means the test passes reliably with the expected audit entry count.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, sql
Domain
databases, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.