-
-
Notifications
You must be signed in to change notification settings - Fork 388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ubuntu jammy s390x: Test failures #1083
Comments
I found good examples using |
I sent the PR #1084. |
I added the https://rubyci.org/ - s390x (Ubuntu) should pass after the next cron build. |
This issue ticket is to manage the test failures on Ubuntu jammy s390x. The cause is same with the the test failures ruby/zlib#60 on ruby/zlib.
The issue summary
On the following environment, the tests are failing.
Here is the used zlib deb package.
Below are the test failures.
As a workaround, we can pass the test With the
DFLTCC=0
.A possible solution
A possible solution is to apply the way used at the pull-request ruby/zlib#63.
Set the environment variable
DFLTCC=0
in a parent Ruby process, then run the spec in a child process. Because theENV['DFLTCC'] = 0
on the parent Ruby process can not affect to the Ruby code on the same process. The zlib spec files common logic can be implemented in the new filelibrary/zlib/spec_helper.rb
.I have one question. In the Ruby's test-unit, there is the
assert_separately
method aserting the test code in a child Ruby process running theEnvUtil.invoke_ruby
internally.https://github.com/ruby/test-unit-ruby-core/blob/c147ebf0de5a172ba4fa252078e56cd4a484abd3/lib/core_assertions.rb#L297-L360
So, is there an equivalent method in
ruby/mspec
orruby/spec
? I found theruby_exe
that looks similar with theEnvUtil.invoke_ruby
.https://github.com/ruby/mspec/blob/b23f052a8d262ebd442e60e23d468ed82852f3d8/lib/mspec/helpers/ruby_exe.rb#L114
The text was updated successfully, but these errors were encountered: