From 9ad85ebe74a72c707a286ce5381f4f10dedb4556 Mon Sep 17 00:00:00 2001 From: Jarek Prokop Date: Tue, 23 Jan 2024 10:12:09 +0100 Subject: [PATCH] Work around infra's networking. TestBundledCA is commented out since some of the build infra can see DNS but then cannot connect. Ideally not even DNS can be resolved for the rubygems.org. The tests always get omitted in builds as long as the infra does not allow connecting outside, which is what we expect as correct behavior from mock. Related: RHEL-36189 --- ruby.spec | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/ruby.spec b/ruby.spec index f61f26c..cf54c79 100644 --- a/ruby.spec +++ b/ruby.spec @@ -892,6 +892,13 @@ MSPECOPTS="" # Avoid `hostname' dependency. %{!?with_hostname:MSPECOPTS="-P 'Socket.gethostname returns the host name'"} +# Some infra allows DNS resolution but then does not allow +# connection to proceed, let's ignore it altogether for now. +# Our expectation is that there is no network connectivity outside +# available loopback interface. That is not the reality currently. +# https://issues.redhat.com/browse/CS-1959 +DISABLE_TESTS="$DISABLE_TESTS -n !/TestBundledCA/" + # Give an option to increase the timeout in tests. # https://bugs.ruby-lang.org/issues/16921 %{?test_timeout_scale:RUBY_TEST_TIMEOUT_SCALE="%{test_timeout_scale}"} \