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.01k stars 3.79k forks source link

roachtest: ruby-pg failed #132418

Open cockroach-teamcity opened 3 days ago

cockroach-teamcity commented 3 days ago

roachtest.ruby-pg failed with artifacts on release-24.2 @ 5405e9098bbc9e12ccc4387664eaedfc2d32e9d9:

(ruby_pg.go:163).func1: all attempts failed for installing gems: full command output in run_095047.396090404_n1_cd-mntdata1rubypg-su.log: COMMAND_PROBLEM: exit status 39
test artifacts and logs in: /artifacts/ruby-pg/run_1

Parameters:

See: roachtest README

See: How To Investigate (internal)

See: Grafana

/cc @cockroachdb/sql-foundations

This test on roachdash | Improve this report!

Jira issue: CRDB-43048

rafiss commented 3 days ago
run_095047.396090404_n1_cd-mntdata1rubypg-su: 2024/10/11 09:50:47 cluster.go:2416: > cd /mnt/data1/ruby-pg/ && sudo bundle install
Don't run Bundler as root. Installing your bundle as root will break this
application for all non-root users on this machine.
Fetching gem metadata from https://rubygems.org/.........
The running version of Bundler (2.5.21) does not match the version of the
specification installed for it (2.3.7). This can be caused by reinstalling Ruby
without removing previous installation, leaving around an upgraded default
version of Bundler. Reinstalling Ruby from scratch should fix the problem.
run_095047.396090404_n1_cd-mntdata1rubypg-su: 2024/10/11 09:50:48 cluster.go:2426: > result: COMMAND_PROBLEM: exit status 39

unclear why this would only fail on this branch