Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 498552 Details for
Bug 634190
=dev-ruby/ffi-1.9.18 fails test on ia64 (tests returning structs): FFI::Struct by value return using pre-set values: Failure/Error: expect(s[:s8]).to eq(0x7f)
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
dev-ruby-ffi-1.9.18-ia64-build.log
dev-ruby-ffi-1.9.18-ia64-build.log (text/x-log), 45.18 KB, created by
Sergei Trofimovich (RETIRED)
on 2017-10-13 17:32:53 UTC
(
hide
)
Description:
dev-ruby-ffi-1.9.18-ia64-build.log
Filename:
MIME Type:
Creator:
Sergei Trofimovich (RETIRED)
Created:
2017-10-13 17:32:53 UTC
Size:
45.18 KB
patch
obsolete
>[32;01m * [39;49;00mPackage: dev-ruby/ffi-1.9.18 >[32;01m * [39;49;00mRepository: gentoo >[32;01m * [39;49;00mMaintainer: ruby@gentoo.org >[32;01m * [39;49;00mUSE: elibc_glibc ia64 kernel_linux ruby_targets_ruby22 test userland_GNU >[32;01m * [39;49;00mFEATURES: preserve-libs sandbox test userpriv usersandbox >>>> Unpacking source... > [32;01m*[0m Running unpack phase for all ... >>>> Unpacking ffi-git-1.9.18.tgz to /var/tmp/portage/dev-ruby/ffi-1.9.18/work/all >>>> Source unpacked in /var/tmp/portage/dev-ruby/ffi-1.9.18/work >>>> Preparing source in /var/tmp/portage/dev-ruby/ffi-1.9.18/work ... > [32;01m*[0m Running prepare phase for all ... > [32;01m*[0m Running source copy phase for ruby22 ... >>>> Source prepared. >>>> Configuring source in /var/tmp/portage/dev-ruby/ffi-1.9.18/work ... > [32;01m*[0m Running configure phase for ruby22 ... >checking for ffi_call() in -lffi... yes >checking for ffi_prep_closure()... yes >checking for ffi_raw_call()... yes >checking for ffi_prep_raw_closure()... yes >checking for shlwapi.h... no >checking for rb_thread_blocking_region()... no >checking for rb_thread_call_with_gvl()... yes >checking for rb_thread_call_without_gvl()... yes >checking for ffi_prep_cif_var()... yes >creating extconf.h >creating Makefile >>>> Source configured. >>>> Compiling source in /var/tmp/portage/dev-ruby/ffi-1.9.18/work ... > [32;01m*[0m Running compile phase for ruby22 ... >make -j5 -l5 -Cext/ffi_c V=1 >make: Entering directory '/var/tmp/portage/dev-ruby/ffi-1.9.18/work/ruby22/ffi-1.9.18/ext/ffi_c' >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o Function.o -c Function.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o FunctionInfo.o -c FunctionInfo.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o Call.o -c Call.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o AbstractMemory.o -c AbstractMemory.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o Struct.o -c Struct.c >[01m[KFunction.c:[m[K In function â[01m[Kasync_cb_event[m[Kâ: >[01m[KFunction.c:563:9:[m[K [01;35m[Kwarning: [m[Kimplicit declaration of function â[01m[Krb_thread_call_without_gvl[m[Kâ [-Wimplicit-function-declaration] > rb_thread_call_without_gvl(async_cb_wait, &w, async_cb_stop, &w); >[01;32m[K ^[m[K >In file included from [01m[KCall.h:36:0[m[K, > from [01m[KFunction.h:48[m[K, > from [01m[KCall.c:57[m[K: >[01m[KCall.c:[m[K In function â[01m[Krbffi_do_blocking_call[m[Kâ: >[01m[KThread.h:78:39:[m[K [01;35m[Kwarning: [m[Kimplicit declaration of function â[01m[Krb_thread_call_without_gvl[m[Kâ [-Wimplicit-function-declaration] > # define rbffi_thread_blocking_region rb_thread_call_without_gvl >[01;32m[K ^[m[K >[01m[KCall.c:355:5:[m[K [01;36m[Knote: [m[Kin expansion of macro â[01m[Krbffi_thread_blocking_region[m[Kâ > rbffi_thread_blocking_region(call_blocking_function, data, (void *) -1, NULL); >[01;32m[K ^[m[K >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o MemoryPointer.o -c MemoryPointer.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o Platform.o -c Platform.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o DynamicLibrary.o -c DynamicLibrary.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o ClosurePool.o -c ClosurePool.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o MethodHandle.o -c MethodHandle.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o Variadic.o -c Variadic.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o DataConverter.o -c DataConverter.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o ArrayType.o -c ArrayType.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o LastError.o -c LastError.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o Type.o -c Type.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o Pointer.o -c Pointer.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o MappedType.o -c MappedType.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o StructByReference.o -c StructByReference.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o Buffer.o -c Buffer.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o ffi.o -c ffi.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o Thread.o -c Thread.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o Types.o -c Types.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o StructByValue.o -c StructByValue.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o StructLayout.o -c StructLayout.c >ia64-unknown-linux-gnu-gcc -I. -I/usr/include/ruby-2.2.0/ia64-linux -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -I/usr/lib/libffi-3.2.1/include -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -O2 -pipe -fdiagnostics-show-option -frecord-gcc-switches -fno-strict-aliasing -fPIC -o LongDouble.o -c LongDouble.c >rm -f ffi_c.so >ia64-unknown-linux-gnu-gcc -shared -o ffi_c.so Function.o FunctionInfo.o Call.o Struct.o AbstractMemory.o MemoryPointer.o Platform.o DynamicLibrary.o ClosurePool.o MethodHandle.o Variadic.o DataConverter.o ArrayType.o LastError.o Type.o Pointer.o MappedType.o StructByReference.o Buffer.o ffi.o Thread.o Types.o StructByValue.o StructLayout.o LongDouble.o -L. -L/usr/lib -L. -Wl,-O1 -Wl,--hash-style=gnu -rdynamic -Wl,-export-dynamic -Wl,--no-undefined -lruby22 -lffi -lffi -lpthread -lgmp -ldl -lcrypt -lm -lc >make: Leaving directory '/var/tmp/portage/dev-ruby/ffi-1.9.18/work/ruby22/ffi-1.9.18/ext/ffi_c' > [32;01m*[0m Running compile phase for all ... >>>> Source compiled. >>>> Test phase: dev-ruby/ffi-1.9.18 > [32;01m*[0m Running test phase for ruby22 ... >"gmake CPU=ia64 OS=linux " >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c BoolTest.c -o BoolTest.o >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c ClosureTest.c -o ClosureTest.o >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c Benchmark.c -o Benchmark.o >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c ReferenceTest.c -o ReferenceTest.o >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c GlobalVariable.c -o GlobalVariable.o >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c PipeHelperWindows.c -o PipeHelperWindows.o >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c PointerTest.c -o PointerTest.o >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c FunctionTest.c -o FunctionTest.o >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c EnumTest.c -o EnumTest.o >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c VariadicTest.c -o VariadicTest.o >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c LastErrorTest.c -o LastErrorTest.o >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c PipeHelperPosix.c -o PipeHelperPosix.o >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c BufferTest.c -o BufferTest.o >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c StringTest.c -o StringTest.o >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c NumberTest.c -o NumberTest.o >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c UnionTest.c -o UnionTest.o >ia64-unknown-linux-gnu-gcc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Wall -Wno-unused -Wno-parentheses -I"." -fPIC -D_REENTRANT -c StructTest.c -o StructTest.o >ia64-unknown-linux-gnu-gcc -o libtest.so -Wl,-O1 -Wl,--hash-style=gnu -shared -Wl,-soname,libtest.so ./BoolTest.o ./ClosureTest.o ./Benchmark.o ./ReferenceTest.o ./GlobalVariable.o ./PipeHelperWindows.o ./PointerTest.o ./FunctionTest.o ./EnumTest.o ./VariadicTest.o ./LastErrorTest.o ./PipeHelperPosix.o ./BufferTest.o ./StringTest.o ./NumberTest.o ./UnionTest.o ./StructTest.o -lm >Run options: exclude {:broken=>true} >............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................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 #<IndexError: Memory access offset=0 size=-1 is out of bounds>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/buffer_spec.rb:168:in `block (2 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 #<RangeError: index+length is greater than size of string>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/buffer_spec.rb:174:in `block (2 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 #<RangeError: index cannot be less than zero>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/buffer_spec.rb:180:in `block (2 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 #<IndexError: Memory access offset=0 size=-1 is out of bounds>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/buffer_spec.rb:210:in `block (2 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 #<RangeError: index+length is greater than size of string>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/buffer_spec.rb:216:in `block (2 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 #<RangeError: index cannot be less than zero>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/buffer_spec.rb:222:in `block (2 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 #<ArgumentError: wrong number of arguments (0 for 2)>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/callback_spec.rb:475:in `block (2 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 `enum' for #<RSpec::ExampleGroups::AllEnums:0x6000000000a11200>>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/enum_spec.rb:420:in `block (2 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 `enum' for #<RSpec::ExampleGroups::AllEnums:0x6000000000a11200>>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/enum_spec.rb:421:in `block (2 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 #<LoadError: no library specified>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/library_spec.rb:81:in `block (2 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 `ret_int8_t' for LibTest:Module>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/number_spec.rb:148: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 `ret_int8_t' for LibTest:Module>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/number_spec.rb:148: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 `ret_u_int8_t' for LibTest:Module>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/number_spec.rb:153: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 `ret_u_int8_t' for LibTest:Module>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/number_spec.rb:153: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 `ret_int16_t' for LibTest:Module>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/number_spec.rb:158: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 `ret_int16_t' for LibTest:Module>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/number_spec.rb:158: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 `ret_u_int16_t' for LibTest:Module>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/number_spec.rb:163: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 `ret_u_int16_t' for LibTest:Module>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/number_spec.rb:163: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 `ret_int32_t' for LibTest:Module>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/number_spec.rb:168: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 `ret_int32_t' for LibTest:Module>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/number_spec.rb:168: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 `ret_u_int32_t' for LibTest:Module>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/number_spec.rb:173: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 `ret_u_int32_t' for LibTest:Module>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/number_spec.rb:173: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 `ptr_ret_int32' for PointerTestLib:Module>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/pointer_spec.rb:58:in `block (2 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 `ptr_ret_int32' for PointerTestLib:Module>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/pointer_spec.rb:62:in `block (2 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 #<IndexError: Memory access offset=0 size=8 is out of bounds>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/rbx/memory_pointer_spec.rb:129:in `block (2 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 #<IndexError: Memory access offset=0 size=4 is out of bounds>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/rbx/memory_pointer_spec.rb:134:in `block (2 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 #<ArgumentError: string contains null byte>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/string_spec.rb:37:in `block (2 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 #<IndexError: Memory access offset=0 size=48 is out of bounds>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/string_spec.rb:104:in `block (2 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 #<IndexError: Memory access offset=-1 size=8 is out of bounds>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/string_spec.rb:116:in `block (2 levels) in <top (required)>'. >...............................................................................................................FF....FF..............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: type of field 0 has zero size>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/struct_spec.rb:858:in `block (2 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 #<IndexError: index 1 out of bounds>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/struct_spec.rb:882:in `block (2 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 #<IndexError: index 1 out of bounds>. 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/ffi-1.9.18/work/ruby22/ffi-1.9.18/spec/ffi/struct_spec.rb:884:in `block (2 levels) in <top (required)>'. >........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... > >Failures: > > 1) FFI::Struct by value return using pre-set values > Failure/Error: expect(s[:s8]).to eq(0x7f) > > expected: 127 > got: 0 > > (compared using ==) > # ./spec/ffi/struct_spec.rb:648:in `block (2 levels) in <top (required)>' > > 2) FFI::Struct by value return using passed in values > Failure/Error: expect(s[:s8]).to eq(123) > > expected: 123 > got: 0 > > (compared using ==) > # ./spec/ffi/struct_spec.rb:654:in `block (2 levels) in <top (required)>' > > 3) FFI::Struct by value parameter, returning struct by value > Failure/Error: expect(ret[:s8]).to eq(s[:s8]) > > expected: 18 > got: 0 > > (compared using ==) > # ./spec/ffi/struct_spec.rb:707:in `block (2 levels) in <top (required)>' > > 4) FFI::Struct by value varargs returning a struct > Failure/Error: expect(s[:len]).to eq(string.length) > > expected: 4 > got: 6291471 > > (compared using ==) > # ./spec/ffi/struct_spec.rb:714:in `block (2 levels) in <top (required)>' > >Finished in 2.21 seconds (files took 18.06 seconds to load) >4845 examples, 4 failures > >Failed examples: > >rspec ./spec/ffi/struct_spec.rb:646 # FFI::Struct by value return using pre-set values >rspec ./spec/ffi/struct_spec.rb:652 # FFI::Struct by value return using passed in values >rspec ./spec/ffi/struct_spec.rb:701 # FFI::Struct by value parameter, returning struct by value >rspec ./spec/ffi/struct_spec.rb:711 # FFI::Struct by value varargs returning a struct > > [31;01m*[0m ERROR: dev-ruby/ffi-1.9.18::gentoo failed (test phase): > [31;01m*[0m (no error message) > [31;01m*[0m > [31;01m*[0m Call stack: > [31;01m*[0m ebuild.sh, line 115: Called src_test > [31;01m*[0m environment, line 4407: Called ruby-ng_src_test > [31;01m*[0m environment, line 4119: Called _ruby_each_implementation 'each_ruby_test' > [31;01m*[0m environment, line 437: Called _ruby_invoke_environment 'ruby22' 'each_ruby_test' > [31;01m*[0m environment, line 558: Called each_ruby_test > [31;01m*[0m environment, line 877: Called die > [31;01m*[0m The specific snippet of code: > [31;01m*[0m CC=$(tc-getCC) CFLAGS="${CFLAGS}" LDFLAGS="${LDFLAGS}" ${RUBY} -S rspec spec || die > [31;01m*[0m > [31;01m*[0m If you need support, post the output of `emerge --info '=dev-ruby/ffi-1.9.18::gentoo'`, > [31;01m*[0m the complete build log and the output of `emerge -pqv '=dev-ruby/ffi-1.9.18::gentoo'`. >!!! When you file a bug report, please include the following information: >GENTOO_VM= CLASSPATH="" JAVA_HOME="" >JAVACFLAGS="" COMPILER="" >and of course, the output of emerge --info =ffi-1.9.18 > [31;01m*[0m The complete build log is located at '/var/tmp/portage/dev-ruby/ffi-1.9.18/temp/build.log'. > [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/dev-ruby/ffi-1.9.18/temp/environment'. > [31;01m*[0m Working directory: '/var/tmp/portage/dev-ruby/ffi-1.9.18/work/ruby22/ffi-1.9.18' > [31;01m*[0m S: '/var/tmp/portage/dev-ruby/ffi-1.9.18/work/ruby22/ffi-1.9.18'
<b>You cannot view the attachment while viewing its details because your browser does not support IFRAMEs. <a href="attachment.cgi?id=498552">View the attachment on a separate page</a>.</b>
View Attachment As Raw
Actions:
View
Attachments on
bug 634190
: 498552
