Jarek Prokop

Example of such build: https://koji.fedoraproject.org/koji/taskinfo?taskID=86641565 Full log: https://gist.github.com/jackorp/f1a0eb00ba616fe52bea594bc2d18be3

I was able to request a ppc64le machine and I think I reproduced the issue. TL;DR it seems like a Ruby 3.1 issue with how this method is implemented. My...

> Does this stuck even happen by the following command on the ppc64le machine you tested? Unfortunately, I had great issues reproducing the infinite loop outside of the test suite...

> @jackorp any progress? The latest info is: clean upstream ruby v3_1_0 works, removing the restriction `"< 3.1"` for `required_ruby_version` from gemspec works as well, with the package AFAICT... I'll...

If we are talking about the distro's vagrant, installed with `zypper install vagrant`, then it works (and it does not throw the exception as described [in previous comment by pvalena](https://github.com/hashicorp/vagrant/pull/12638#issuecomment-1046911601))...

Hmm, putting a debug output ```Cpp std::cout

We looked at this issue closer, and it seems to be composed of SELinux, FFI Closure, and Forking the Ruby process. From the [linked bug](https://bugzilla.redhat.com/show_bug.cgi?id=2040380#c6): "In modern libffi 3.4.2 we...

Thanks for the patch! It improved the situation somewhat but not complemetely. After uncomentting and re-enabling the tests for Ruby and applying the patch I observe new issue in the...

Hmm, not better. I also applied the previous commit with `GC.start` to ensure application of the `a0ccc6b` without modifying the patch too much. I am seeing similar failures as before....

Thanks! The state is Much better now. However this error [from the logs](https://kojipkgs.fedoraproject.org//work/tasks/2723/92032723/build.log) is puzzling: ``` 1) Error: Fiddle::TestClosure#test_free: NoMethodError: undefined method `assert_false' for #nil, :retry=>true, :hide_skip=>true, :repeat_count=>nil, :excludes=>["./test/excludes"], :ruby=>["./miniruby",...