[#7955] Failing tests in ruby since 1.8.2 — "Caleb Tennis" <caleb@...>
The following tests have been failing in Ruby for a long time, including
[#7978] Patch for Unix socket peer credentials — "James F. Hranicky" <jfh@...>
This patch adds support for getting the uid and gid of the peer
In article <200606091528.30171.jfh@cise.ufl.edu>,
On Friday 16 June 2006 11:51, Tanaka Akira wrote:
In article <200606161327.35948.jfh@cise.ufl.edu>,
On Saturday 17 June 2006 06:27, Tanaka Akira wrote:
In article <200607101352.16804.jfh@cise.ufl.edu>,
On Tuesday 11 July 2006 00:10, Tanaka Akira wrote:
Hi,
On Thursday 13 July 2006 22:48, nobu@ruby-lang.org wrote:
On Jul 18, 2006, at 12:27 PM, James F. Hranicky wrote:
On Tuesday 18 July 2006 15:52, Eric Hodel wrote:
[#7994] Ruby Kaigi date confusion — "Charles O Nutter" <headius@...>
I'm quite confused by the dates I have seen reported on various Ruby Kaigi
[#8013] Download page on ruby-lang has numeric URL — Hugh Sasse <hgs@...>
This is off-topic to ruby-core, but possibly core to ruby's uptake:
On Jun 19, 2006, at 3:32 AM, Hugh Sasse wrote:
[#8038] bug in $. ? — Wybo Dekker <wybo@...>
wybo>cat t
Wybo Dekker schrieb:
Pit Capitain wrote:
[#8050] Thank-you to the Rails Core Team — Dave Teare <devlists-ruby-core@...>
While we were listening to Dave Thomas' Keynote address today at
[#8061] Win32 Extension Issues Wanted! — "Austin Ziegler" <halostatue@...>
Everyone. I had a conversation with folks from Microsoft today about
[#8065] Core documentation patches — Alex Young <alex@...>
Hi there,
Hi,
Yukihiro Matsumoto wrote:
[#8073] 1.8.5p1 build failure on Solaris 10 — "Daniel Berger" <Daniel.Berger@...>
Solaris 10
Hi,
Yukihiro Matsumoto wrote:
>>>>> "D" == Daniel Berger <Daniel.Berger@qwest.com> writes:
ts <decoux@moulon.inra.fr> wrote on 28.06.2006 17:37:00:
Hi,
Yukihiro Matsumoto <matz@ruby-lang.org> wrote on 29.06.2006 20:02:11:
Hi,
Yukihiro Matsumoto <matz@ruby-lang.org> wrote on 29.06.2006 20:53:20:
ville.mattila@stonesoft.com wrote:
[#8087] optparse.rb to RDoc documentation patch — <noreply@...>
Patches item #4879, was opened at 2006-06-28 20:50
On Jun 28, 2006, at 11:50 AM, <noreply@rubyforge.org>
[#8102] Reorganizing configure.in by platform? — "Daniel Berger" <Daniel.Berger@...>
Hi,
Two test failures with 1.8.5p1, Solaris 10
Hi,
Solaris 10
gcc 3.4.5
built with -std=gnu99
The good news is that 1.8.5p1 gets through make test-all without segfaulting. Yay!
I did get two test failures when I ran make test-all, however:
1) Failure:
test_seqpacket_pair(TestUNIXSocket) [./socket/test_unix.rb:148]:
<""> expected but was
<"haha">.
2) Failure:
test_cgi(TestWEBrickCGI)
[./webrick/test_cgi.rb:27:in `test_cgi'
/export/home/djberge/local/src/ruby/ruby-1.8.5/lib/net/http.rb:1047:in
`request'
/export/home/djberge/local/src/ruby/ruby-1.8.5/lib/net/http.rb:2102:in
`reading_body'
/export/home/djberge/local/src/ruby/ruby-1.8.5/lib/net/http.rb:1046:in
`request'
/export/home/djberge/local/src/ruby/ruby-1.8.5/lib/net/http.rb:1031:in
`request'
/export/home/djberge/local/src/ruby/ruby-1.8.5/lib/net/http.rb:543:in `start'
/export/home/djberge/local/src/ruby/ruby-1.8.5/lib/net/http.rb:1029:in
`request'
./webrick/test_cgi.rb:27:in `test_cgi'
./webrick/utils.rb:26:in `start_server'
./webrick/utils.rb:34:in `start_httpserver'
./webrick/test_cgi.rb:24:in `test_cgi']:
<"/webrick.cgi"> expected but was
<"<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.0//EN\">\n<HTML>\n
<HEAD><TITLE>Internal Server Error</TITLE></HEAD>\n <BODY>\n <H1>Internal
Server Error</H1>\n Premature end of script headers:
/export/home/djberge/local/src/ruby/ruby-1.8.5/test/webrick/webrick.cgi\n
<HR>\n <ADDRESS>\n WEBrick/1.3.1 (Ruby/1.8.5/2006-06-22) OpenSSL/0.9.8a
at\n 127.0.0.1:33328\n </ADDRESS>\n </BODY>\n</HTML>\n">.
1565 tests, 15560 assertions, 2 failures, 0 errors
*** Error code 1
make: Fatal error: Command failed for target `test-all'
Regards,
Dan
This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.