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

roachtest: ruby-pg failed #99546

Closed
cockroach-teamcity opened this issue Mar 25, 2023 · 3 comments · Fixed by #99761
Closed

roachtest: ruby-pg failed #99546

cockroach-teamcity opened this issue Mar 25, 2023 · 3 comments · Fixed by #99761
Labels
branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.1 C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Mar 25, 2023

roachtest.ruby-pg failed with artifacts on release-23.1 @ 52e55d2ef172b7cfec14e8a0a954f8864b2be779:

test artifacts and logs in: /artifacts/ruby-pg/run_1
(test_runner.go:1008).runTest: test timed out (10h0m0s)
(orm_helpers.go:212).summarizeFailed: 
Tests run on Cockroach v23.1.0-alpha.7-dev-52e55d2ef172b7cfec14e8a0a954f8864b2be779
Tests run against ruby-pg v1.3.5
161 Total Tests Run
123 tests passed
38 tests failed
0 tests skipped
0 tests ignored
166 tests passed unexpectedly
0 tests failed unexpectedly
0 tests expected failed but skipped
166 tests expected failed but not run
---
For a full summary look at the ruby-pg artifacts
An updated blocklist (rubyPGBlocklist) is available in the artifacts' ruby-pg log

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

Same failure on other branches

/cc @cockroachdb/sql-sessions

This test on roachdash | Improve this report!

Jira issue: CRDB-25922

@cockroach-teamcity cockroach-teamcity added branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.1 C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions) labels Mar 25, 2023
@cockroach-teamcity cockroach-teamcity added this to the 23.1 milestone Mar 25, 2023
@cockroach-teamcity
Copy link
Member Author

roachtest.ruby-pg failed with artifacts on release-23.1 @ f351747ed97862fc037717cadec23f18073fb6be:

test artifacts and logs in: /artifacts/ruby-pg/run_1
(test_runner.go:1008).runTest: test timed out (10h0m0s)
(orm_helpers.go:212).summarizeFailed: 
Tests run on Cockroach v23.1.0-alpha.8-dev-f351747ed97862fc037717cadec23f18073fb6be
Tests run against ruby-pg v1.3.5
170 Total Tests Run
133 tests passed
37 tests failed
0 tests skipped
0 tests ignored
167 tests passed unexpectedly
0 tests failed unexpectedly
0 tests expected failed but skipped
167 tests expected failed but not run
---
For a full summary look at the ruby-pg artifacts
An updated blocklist (rubyPGBlocklist) is available in the artifacts' ruby-pg log

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

Same failure on other branches

This test on roachdash | Improve this report!

@rafiss rafiss removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label Mar 26, 2023
@cockroach-teamcity
Copy link
Member Author

roachtest.ruby-pg failed with artifacts on release-23.1 @ b995ddff53ee95a30537a366c6cd8e0e13fcee79:

test artifacts and logs in: /artifacts/ruby-pg/run_1
(test_runner.go:1008).runTest: test timed out (10h0m0s)
(orm_helpers.go:212).summarizeFailed: 
Tests run on Cockroach v23.1.0-alpha.8-dev-b995ddff53ee95a30537a366c6cd8e0e13fcee79
Tests run against ruby-pg v1.3.5
175 Total Tests Run
160 tests passed
15 tests failed
0 tests skipped
0 tests ignored
189 tests passed unexpectedly
0 tests failed unexpectedly
0 tests expected failed but skipped
189 tests expected failed but not run
---
For a full summary look at the ruby-pg artifacts
An updated blocklist (rubyPGBlocklist) is available in the artifacts' ruby-pg log

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

Same failure on other branches

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

roachtest.ruby-pg failed with artifacts on release-23.1 @ 186218edb86b5974501b2976cfd0704d4d6d1beb:

test artifacts and logs in: /artifacts/ruby-pg/run_1
(test_runner.go:1008).runTest: test timed out (10h0m0s)
(orm_helpers.go:212).summarizeFailed: 
Tests run on Cockroach v23.1.0-alpha.8-dev-186218edb86b5974501b2976cfd0704d4d6d1beb
Tests run against ruby-pg v1.3.5
224 Total Tests Run
209 tests passed
15 tests failed
0 tests skipped
0 tests ignored
189 tests passed unexpectedly
0 tests failed unexpectedly
0 tests expected failed but skipped
189 tests expected failed but not run
---
For a full summary look at the ruby-pg artifacts
An updated blocklist (rubyPGBlocklist) is available in the artifacts' ruby-pg log

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

Same failure on other branches

This test on roachdash | Improve this report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.1 C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants