[BUG] ./spec/ruby/1.8/library/ipaddr/new_spec.rb fails on ubuntu
Reported by Le Huy | April 4th, 2008 @ 04:20 AM | in 1.0 preview
2)
IPAddr#new it should initialize IPAddr ipv6 address with long notation ERROR
invalid address
IPAddr#in6_addr at /u01/rubinius/code/lib/ipaddr.rb:464
IPAddr#initialize at /u01/rubinius/code/lib/ipaddr.rb:432
Class#new at kernel/bootstrap/class.rb:16
Object#__script__ {} at ./spec/ruby/1.8/library/ipaddr/new_spec.rb:19
Proc#call at kernel/core/proc.rb:84
MSpec.protect at ./mspec/runner/mspec.rb:116
RunState#protect {} at ./mspec/runner/state.rb:46
Array#each at kernel/core/array.rb:573
RunState#protect at ./mspec/runner/state.rb:46
RunState#process {} at ./mspec/runner/state.rb:64
Array#each at kernel/core/array.rb:573
RunState#process at ./mspec/runner/state.rb:68
MSpec.describe at ./mspec/runner/mspec.rb:21
Object#describe at ./mspec/runner/object.rb:11
Object#__script__ at ./spec/ruby/1.8/library/ipaddr/new_spec.rb:4
CompiledMethod#as_script at kernel/core/compiled_method.rb:326
Compile.single_load at kernel/core/compile.rb:233
Compile.unified_load at kernel/core/compile.rb:113
Kernel.load at kernel/core/compile.rb:390
MSpec.files {} at ./mspec/runner/mspec.rb:37
Proc#call at kernel/core/proc.rb:84
MSpec.protect at ./mspec/runner/mspec.rb:112
MSpec.files {} at ./mspec/runner/mspec.rb:38
Array#each at kernel/core/array.rb:573
MSpec.files at ./mspec/runner/mspec.rb:34
MSpec.process at ./mspec/runner/mspec.rb:27
MSpecRun#run at mspec/bin/mspec-run:74
MSpecRun.main at ./mspec/bin/script.rb:65
Object#__script__ at mspec/bin/mspec-run:79
CompiledMethod#as_script at kernel/core/compiled_method.rb:326
Compile.single_load at kernel/core/compile.rb:233
Compile.load_from_extension at kernel/core/compile.rb:310
Object#__script__ at kernel/loader.rb:190
Comments and changes to this ticket
-
Eero Saynatkari April 5th, 2008 @ 12:34 AM
- → State changed from new to open
Looks clear for me at least as of 22f30423. Can you double-check and post platform details if you still see it?
-
Dirkjan Bussink April 5th, 2008 @ 12:46 AM
Be sure to run rake distclean first, this looks like the same problem that was fixed by the new version of oniguruma I've included some time ago.
-
Dirkjan Bussink April 6th, 2008 @ 10:49 AM
Are you still able to reproduce this? Or did the rake distclean fix it?
-
-
Dirkjan Bussink April 7th, 2008 @ 11:12 AM
- → State changed from open to resolved
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
