cockroachdb / cockroachdb/cockroach
release-26.2.7-rc: roachtest: node-postgres failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
roachtest.node-postgres [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyGcePrivateBazel/21511417?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyGcePrivateBazel/21511417?buildTab=artifacts#/node-postgres) on release-26.2.7-rc @ [6f643133d9a96ff138ee71d0f9a151a1a8595fba](https://github.com/cockroachdb/cockroach/commits/6f643133d9a96ff138ee71d0f9a151a1a8595fba):
Failed with:
```
(orm_helpers.go:225).summarizeFailed:
Tests run on Cockroach v26.2.7-dev-6f643133d9a96ff138ee71d0f9a151a1a8595fba
Tests run against node-postgres N/A
172 Total Tests Run
171 tests passed
1 test failed
2 tests skipped
2 tests ignored
0 tests passed unexpectedly
1 test failed unexpectedly
0 tests expected failed but skipped
0 tests expected failed but not run
---
--- FAIL: connection timeout => should timeout on query if all clients are busy - unknown (unexpected)
For a full summary look at the node-postgres artifacts
An updated blocklist (nodePostgresBlockList) is available in the artifacts' node-postgres log
test artifacts and logs in: /artifacts/node-postgres/run_1
```
Cluster Node to Ip Mapping:
| Node | Public IP | Private IP |
| --- | --- | --- |
| teamcity-21511417-1789103297-202-n1cpu4-0001 | | 10.91.98.158 |
Parameters:
- arch=amd64
- cloud=gce
- coverageBuild=false
- cpu=4
- diskCount=0
- encrypted=false
- fs=ext4
- localSSD=true
- metamorphicLeases=leader
- metamorphicWriteBuffering=true
- runtimeAssertionsBuild=false
Help
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
See: [Grafana](https://go.crdb.dev/roachtest-grafana/teamcity-21511417/node-postgres/1789128356781/1789128688433)
/cc @cockroachlabs/sql-foundations
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*node-postgres.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Jira issue: CRDB-68186
Contributor guide
Research direction
Start with the linked TeamCity node-postgres artifacts and logs under /artifacts/node-postgres/run_1, then read pkg/cmd/roachtest/README.md and the failure summary. Use the Grafana link and updated nodePostgresBlockList to determine whether the timeout is reproducible. Done means the unexpected failure is resolved and the roachtest passes on release-26.2.7-rc.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- databases, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100