Bug #13834: RubyGems test suite occasionally changes working directory and breaks the rest of test suite

• Status: Closed
• Assignee: hsbt (Hiroshi SHIBATA)
• Target version: -
• ruby -v: ruby 2.5.0dev (2017-08-18 trunk 59616) [x86_64-linux]
• Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: REQUIRED

[vo.x (Vit Ondruch)]

From time to time, RubyGems test suite changes working directory, which breaks rest of Ruby tests suite. It all starts like this:

[ 7096/17125] TestGemRemoteFetcher#test_do_not_allow_invalid_client_cert_auth_connection = 0.01 sLeaked file descriptor: TestGemRemoteFetcher#test_do_not_allow_invalid_client_cert_auth_connection: 21 : #<TCPServer:fd 21, AF_INET, 0.0.0.0, 45301>
Leaked file descriptor: TestGemRemoteFetcher#test_do_not_allow_invalid_client_cert_auth_connection: 22 : #<TCPServer:fd 22, AF_INET6, ::, 45301>
Leaked file descriptor: TestGemRemoteFetcher#test_do_not_allow_invalid_client_cert_auth_connection: 23 : #<IO:fd 23>
Leaked file descriptor: TestGemRemoteFetcher#test_do_not_allow_invalid_client_cert_auth_connection: 24 : #<IO:fd 24>
Leaked thread: TestGemRemoteFetcher#test_do_not_allow_invalid_client_cert_auth_connection: #<Thread:0x000056191465fe40@/home/hsbt/chkbuild/tmp/build/20170818T003002Z/ruby/test/rubygems/test_gem_remote_fetcher.rb:1025 sleep>
Environment variable changed: TestGemRemoteFetcher#test_do_not_allow_invalid_client_cert_auth_connection : "GEM_PRIVATE_KEY_PASSPHRASE" added
Environment variable changed: TestGemRemoteFetcher#test_do_not_allow_invalid_client_cert_auth_connection : "GEM_SPEC_CACHE" added
Environment variable changed: TestGemRemoteFetcher#test_do_not_allow_invalid_client_cert_auth_connection : "HOME" changed : "/home/hsbt" -> "/home/hsbt/chkbuild/tmp/build/20170818T003002Z/tmp/test_rubygems_29019/userhome"

and results in errors such as:

  2) Failure:
TestMkmf::TestConfig#test_dir_config [/home/hsbt/chkbuild/tmp/build/20170818T003002Z/ruby/test/mkmf/test_config.rb:12]:
assert_separately failed with error message
pid 2383 exit 1
| /home/hsbt/chkbuild/tmp/build/20170818T003002Z/ruby/lib/mkmf.rb:228:in `expand_path': No such file or directory - getcwd (Errno::ENOENT)
| 	from /home/hsbt/chkbuild/tmp/build/20170818T003002Z/ruby/lib/mkmf.rb:228:in `<module:MakeMakefile>'
| 	from /home/hsbt/chkbuild/tmp/build/20170818T003002Z/ruby/lib/mkmf.rb:48:in `<top (required)>'
| 	from -:1:in `require'

You can find the full log rubyci.org 1.

[vo.x (Vit Ondruch)]

I also opened RubyGems ticket:

https://github.com/rubygems/rubygems/issues/1991

[shevegen (Robert A. Heiler)]

I think the github "ticket" is not as useful as the issue track here; I may mistakingly remember
but I think that some of the ruby core team said so. Where github may help of course are
patches and pull requests attached to.

The error "No such file or directory - getcwd (Errno::ENOENT)" may have come from some operation
removing a directory so perhaps the logic in the build-up chain is incorrect. BTW I also see
this on ruby-gnome sometimes, with paths such as "/home/hsbt/chkbuild/tmp/build/" (or ruby-gnome,
it's kou though, not hsbt) - is this general that this path information is included somewhere? It
may be easier to instead use some ENV variable or something, since it is strange that other users
get to see such paths in general. (I just noticed it in ruby-gnome a while ago, now I notice it
here.)

[vo.x (Vit Ondruch)]

So far, I think the test never reaches this 1 line for some reason. Or if it reaches it, it is not executed properly. Then the temporary directory is cleaned up and the test suite starts to fail.

[vo.x (Vit Ondruch)]

Another instance of this bug:

http://rubyci.s3.amazonaws.com/fedora26/ruby-trunk/log/20170919T063002Z.log.html.gz

[hsbt (Hiroshi SHIBATA)]

• Status changed from Open to Assigned
• Assignee set to hsbt (Hiroshi SHIBATA)

[hsbt (Hiroshi SHIBATA)]

• Status changed from Assigned to Feedback

@vo.x (Vit Ondruch)

Do you still have this issue? I couldn't reproduce this on Fedora 27 and 28 of RubyCI.

[jeremyevans0 (Jeremy Evans)]

• Status changed from Feedback to Closed