6.0-stable build 193

Revision r24854 (build 193 started on 2026-07-21T15:34:49Z)


originally caused by:
 Started by an SCM change
Building in workspace /var/lib/jenkins/workspace/6.0-stable/DATABASE_ADAPTER/postgresql/RUBY_VER/ruby-3.2
Updating http://svn.redmine.org/redmine/branches/6.0-stable at revision '2026-07-21T08:34:49.437 -0700'
U         app/controllers/account_controller.rb
U         app/helpers/application_helper.rb
U         test/functional/account_controller_test.rb
U         test/helpers/application_helper_test.rb
 U        .
At revision 24854

[ruby-3.2] $ /bin/sh -xe /tmp/jenkins4798341686699470735.sh
+ rm -f config/database.yml
+ echo ActiveRecord::Tasks::DatabaseTasks::LOCAL_HOSTS << "192.168.1.70"
[ruby-3.2] $ /bin/sh -xe /tmp/jenkins3429910757627414954.sh
+ PATH=/var/lib/jenkins/ruby/ruby-3.2/bin:/var/lib/jenkins/.rbenv/shims:/var/lib/jenkins/.rbenv/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games rake -f lib/tasks/ci.rake config/database.yml BRANCH=6.0-stable CI_PG_HOST=192.168.1.70 CI_MYSQL_HOST=192.168.1.70
[ruby-3.2] $ /bin/sh -xe /tmp/jenkins6132754663318860409.sh
+ PATH=/var/lib/jenkins/ruby/ruby-3.2/bin:/var/lib/jenkins/.rbenv/shims:/var/lib/jenkins/.rbenv/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games bundle update
Fetching gem metadata from https://rubygems.org/.........
Resolving dependencies...
WARN: Unresolved or ambiguous specs during Gem::Specification.reset:
      stringio (>= 0)
      Available/installed versions of this gem:
      - 3.2.0
      - 3.1.9
      - 3.1.8
      - 3.1.7
      - 3.1.6
      - 3.1.5
      - 3.1.3
      - 3.1.2
      - 3.1.1
      - 3.1.0
      - 3.0.9
      - 3.0.4
WARN: Clearing out unresolved specs. Try 'gem cleanup <gem>'
Please report a bug if this causes problems.
Using concurrent-ruby 1.3.8 (was 1.3.6)
Using cgi 0.5.2 (was 0.5.1)
Using crass 1.0.7 (was 1.0.6)
Using erb 6.0.6 (was 6.0.4)
Using json 2.21.1 (was 2.19.9)
Using language_server-protocol 3.17.0.6 (was 3.17.0.5)
Using yard 0.9.45 (was 0.9.44)
Using websocket-driver 0.8.2 (was 0.8.1)
Using nokogiri 1.19.4 (was 1.19.3)
Using parser 3.3.12.0 (was 3.3.11.1)
Using pp 0.6.4 (was 0.6.3)
Using net-imap 0.4.25 (was 0.4.24)
Using loofah 2.25.2 (was 2.25.1)
Using rails-html-sanitizer 1.7.1 (was 1.7.0)
Using globalid 1.4.0 (was 1.3.0)
Using rdoc 8.0.0 (was 7.2.0)
Bundle updated!
2 installed gems you directly depend on are looking for funding.
  Run `bundle fund` for details
[ruby-3.2] $ /bin/sh -xe /tmp/jenkins7269361362070943554.sh
+ PATH=/var/lib/jenkins/ruby/ruby-3.2/bin:/var/lib/jenkins/.rbenv/shims:/var/lib/jenkins/.rbenv/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games SCMS=subversion,git,mercurial,filesystem,bazaar,cvs bundle exec rake ci:about ci:setup db:environment:set RAILS_ENV=test
could not connect to server: No route to host
	Is the server running on host "192.168.1.70" and accepting
	TCP/IP connections on port 5432?
Couldn't create 'ci_60stable_ruby32_dev' database. Please check your configuration.
rake aborted!
ActiveRecord::ConnectionNotEstablished: could not connect to server: No route to host (ActiveRecord::ConnectionNotEstablished)
	Is the server running on host "192.168.1.70" and accepting
	TCP/IP connections on port 5432?
/var/lib/jenkins/workspace/6.0-stable/DATABASE_ADAPTER/postgresql/RUBY_VER/ruby-3.2/lib/tasks/ci.rake:38:in `block (2 levels) in <top (required)>'
/var/lib/jenkins/ruby/ruby-3.2/bin/bundle:25:in `load'
/var/lib/jenkins/ruby/ruby-3.2/bin/bundle:25:in `<main>'

Caused by:
PG::ConnectionBad: could not connect to server: No route to host (PG::ConnectionBad)
	Is the server running on host "192.168.1.70" and accepting
	TCP/IP connections on port 5432?
/var/lib/jenkins/workspace/6.0-stable/DATABASE_ADAPTER/postgresql/RUBY_VER/ruby-3.2/lib/tasks/ci.rake:38:in `block (2 levels) in <top (required)>'
/var/lib/jenkins/ruby/ruby-3.2/bin/bundle:25:in `load'
/var/lib/jenkins/ruby/ruby-3.2/bin/bundle:25:in `<main>'
Tasks: TOP => db:create:all
(See full trace by running task with --trace)
Ruby version: 3.2.2-p53 (2023-03-30) [i686-linux]
Build step 'Execute shell' marked build as failure
Finished: FAILURE