ruby.git/test/socket, branch v3_1_6 The Ruby Programming Language merge revision(s) 195e32977f181c8af9233a12cfc2c98e0f7957f6: 2023-03-25T07:06:44+00:00 nagachika nagachika@ruby-lang.org 2023-03-25T07:06:44+00:00 e66b7917d79d87121d9ee7b3d3048319e9faefb8 Skip test_udp_server on s390x RHEL 7.1 It seems like it never succeeds on this CI. --- test/socket/test_socket.rb | 4 ++++ 1 file changed, 4 insertions(+) 
	Skip test_udp_server on s390x RHEL 7.1

	It seems like it never succeeds on this CI.
	---
	 test/socket/test_socket.rb | 4 ++++
	 1 file changed, 4 insertions(+)
Prepare for removing RubyVM::JIT (#5262) 2021-12-14T07:07:46+00:00 Takashi Kokubun takashikkbn@gmail.com 2021-12-14T07:07:46+00:00 1a63468831524f68e73cbb068071652c6486cfc6 






Revert "test/socket/test_socket.rb: skip on Solaris"
2021-11-29T15:07:30+00:00

Naohisa Goto
ngotogenome@gmail.com

2021-11-29T15:07:30+00:00

f8f2885bd0b42b99703910eae78c03fef6458833

This reverts commit 27fb9d272daaae89089dfb61849ebe8e7aa6c833.

The test failure on Solaris 10 is due to incomplete IPv6 configuration
on the CI server, that have already been fixed.

Reference for the fix: https://centrify.force.com/support/Article/KB-1179-X11-Forwarding-fails-with-Centrify-OpenSSH-5-0-Solaris/





This reverts commit 27fb9d272daaae89089dfb61849ebe8e7aa6c833.

The test failure on Solaris 10 is due to incomplete IPv6 configuration
on the CI server, that have already been fixed.

Reference for the fix: https://centrify.force.com/support/Article/KB-1179-X11-Forwarding-fails-with-Centrify-OpenSSH-5-0-Solaris/







Use Test::Unit::AssertionFailedError instead of MiniTest::Assertion for test-unit migration
2021-09-06T09:34:15+00:00

Hiroshi SHIBATA
hsbt@ruby-lang.org

2021-09-06T09:34:15+00:00

940a19e4b3ae1ce466c3bc912175b4ef7c615c53












test/socket/test_socket.rb: skip on Solaris
2021-07-29T04:51:43+00:00

Yusuke Endoh
mame@ruby-lang.org

2021-07-29T04:49:35+00:00

27fb9d272daaae89089dfb61849ebe8e7aa6c833

The test fails on Solaris 10. Maybe due to the IPv6 configuration on the
server, but I have no idea at all. I've asked @ngoto to investigate the
issue, so will tentatively skip the tests on Solaris

http://rubyci.s3.amazonaws.com/solaris10-gcc/ruby-master/log/20210729T040002Z.fail.html.gz





The test fails on Solaris 10. Maybe due to the IPv6 configuration on the
server, but I have no idea at all. I've asked @ngoto to investigate the
issue, so will tentatively skip the tests on Solaris

http://rubyci.s3.amazonaws.com/solaris10-gcc/ruby-master/log/20210729T040002Z.fail.html.gz







Get rid of sporadic WSAEACCES on Windows [ruby-dev:42661]
2021-05-21T09:26:07+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2021-05-20T11:15:43+00:00

e9974a466ac7edcb8035f5f7bc65c4c6731e2ee2












Get rid of sporadic WSAEACCES on Windows [ruby-dev:42661]
2021-05-20T12:56:58+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2021-05-20T11:15:43+00:00

c71109355987f290257e977c1634db6328916786












Fixed FD leaks
2021-03-08T01:08:40+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2021-03-08T01:08:18+00:00

d0a05fd4b40ff0f88728c4897e67b68185128f54












added mutexes for socket and connection lists on win32
2021-02-23T07:20:01+00:00

Andrew Aladjev
aladjev.andrew@gmail.com

2021-02-22T22:35:01+00:00

0d76636117c99921ac7c43293ba7962d22e72fbd












Rename RubyVM::MJIT to RubyVM::JIT
2021-01-14T06:46:51+00:00

Takashi Kokubun
takashikkbn@gmail.com

2021-01-14T06:36:45+00:00

e1fee7f949cb6719122672fa1081c60984a5339f

because the name "MJIT" is an internal code name, it's inconsistent with
--jit while they are related to each other, and I want to discourage future
JIT implementation-specific (e.g. MJIT-specific) APIs by this rename.

[Feature #17490]





because the name "MJIT" is an internal code name, it's inconsistent with
--jit while they are related to each other, and I want to discourage future
JIT implementation-specific (e.g. MJIT-specific) APIs by this rename.

[Feature #17490]