Work around infra's networking.
TestGemBundledCA 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-17090
This commit is contained in:
parent
4f8991cc06
commit
b7269a7788
@ -1093,6 +1093,13 @@ MSPECOPTS=""
|
|||||||
export DFLTCC=0
|
export DFLTCC=0
|
||||||
%endif
|
%endif
|
||||||
|
|
||||||
|
# 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 !/TestGemBundledCA/"
|
||||||
|
|
||||||
# Give an option to increase the timeout in tests.
|
# Give an option to increase the timeout in tests.
|
||||||
# https://bugs.ruby-lang.org/issues/16921
|
# https://bugs.ruby-lang.org/issues/16921
|
||||||
%{?test_timeout_scale:RUBY_TEST_TIMEOUT_SCALE="%{test_timeout_scale}"} \
|
%{?test_timeout_scale:RUBY_TEST_TIMEOUT_SCALE="%{test_timeout_scale}"} \
|
||||||
|
Loading…
Reference in New Issue
Block a user