https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-ruby/rubyntlm-0.6.3-r1 fails tests. Discovered on: amd64 (internal ref: tinderbox_musl) System: MUSL-SYSTEM (https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#MUSL) Info about the issue: https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#CF0015
Created attachment 884026 [details] build.log build log and emerge --info
Error(s) that match a know pattern: Failure/Error: OpenSSL::Digest::MD4.digest pwd Failure/Error: dec = OpenSSL::Cipher.new("des-cbc").encrypt OpenSSL::Cipher::CipherError: OpenSSL::Digest::DigestError: Failure/Error: OpenSSL::Cipher.new("rc4").random_key Failure/Error: OpenSSL::Digest::MD4.digest pwd Failure/Error: rc4 = OpenSSL::Cipher.new("rc4") OpenSSL::Cipher::CipherError: OpenSSL::Digest::DigestError: .........................................................................FFFFF.........................................................................WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<TypeError: no implicit conversion of String into Integer>. Instead consider providing a specific error class or message. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. Called from /var/tmp/portage/dev-ruby/rubyntlm-0.6.3-r1/work/ruby31/rubyntlm-0.6.3/spec/support/shared/examples/net/ntlm/int_shared.rb:17:in `block (3 levels) in <top (required)>'. ............WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<NoMethodError: undefined method `&' for "A":String ............WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<TypeError: no implicit conversion of String into Integer>. Instead consider providing a specific error class or message. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. Called from /var/tmp/portage/dev-ruby/rubyntlm-0.6.3-r1/work/ruby31/rubyntlm-0.6.3/spec/support/shared/examples/net/ntlm/int_shared.rb:17:in `block (3 levels) in <top (required)>'. .WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<NoMethodError: undefined method `>>' for nil:NilClass .WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<TypeError: no implicit conversion of nil into Integer>. Instead consider providing a specific error class or message. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. Called from /var/tmp/portage/dev-ruby/rubyntlm-0.6.3-r1/work/ruby31/rubyntlm-0.6.3/spec/support/shared/examples/net/ntlm/int_shared.rb:22:in `block (3 levels) in <top (required)>'.
