On Oct 10, 2010, at 1:06 AM, [email protected] wrote:

…

>     [java] 
>     [java] 
>     [java] 1)
>     [java] File.ftype returns 'socket' when the file is a socket ERROR
>     [java] ArgumentError: too long unix socket path (max: 103bytes)
>     [java] 
> <http://ci.jruby.org/job/jruby-test-matrix/./jdk=ibm-java-6,testtype=spec-ci/ws/spec/ruby/core/file/fixtures/file_types.rb>:60:in
>  `socket'
>     [java] 
> <http://ci.jruby.org/job/jruby-test-matrix/./jdk=ibm-java-6,testtype=spec-ci/ws/spec/ruby/core/file/ftype_spec.rb>:62
>     [java] 
> <http://ci.jruby.org/job/jruby-test-matrix/./jdk=ibm-java-6,testtype=spec-ci/ws/spec/ruby/core/file/ftype_spec.rb>:4
>     [java] 
> <http://ci.jruby.org/job/jruby-test-matrix/./jdk=ibm-java-6,testtype=spec-ci/ws/spec/ruby/core/file/ftype_spec.rb>:56:in
>  `load'
>     [java] 
>     [java] 2)
>     [java] File::Stat#ftype returns 'socket' when the file is a socket ERROR
>     [java] ArgumentError: too long unix socket path (max: 103bytes)
>     [java] 
> <http://ci.jruby.org/job/jruby-test-matrix/./jdk=ibm-java-6,testtype=spec-ci/ws/spec/ruby/core/file/fixtures/file_types.rb>:60:in
>  `socket'
>     [java] 
> <http://ci.jruby.org/job/jruby-test-matrix/./jdk=ibm-java-6,testtype=spec-ci/ws/spec/ruby/core/file/stat/ftype_spec.rb>:54
>     [java] 
> <http://ci.jruby.org/job/jruby-test-matrix/./jdk=ibm-java-6,testtype=spec-ci/ws/spec/ruby/core/file/stat/ftype_spec.rb>:4
>     [java] 
> <http://ci.jruby.org/job/jruby-test-matrix/./jdk=ibm-java-6,testtype=spec-ci/ws/spec/ruby/core/file/stat/ftype_spec.rb>:56:in
>  `load'
>     [java] 
>     [java] Finished in 857.179000 seconds
>     [java] 
>     [java] 2858 files, 11832 examples, 38822 expectations, 0 failures, 2 
> errors
>     [java] Java Result: 1

Where is

ArgumentError: too long unix socket path (max: 103bytes)

coming from? Is it Ruby code somewhere? Or is it J9 that's being stupid?


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to