Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 411191 - =dev-ruby/httpclient-2.2.2 fails tests (HTTPAccess2::TestClient) [./test/test_http-access2.rb]
Summary: =dev-ruby/httpclient-2.2.2 fails tests (HTTPAccess2::TestClient) [./test/test...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Ruby Team
URL: https://github.com/nahi/httpclient/is...
Whiteboard:
Keywords:
Depends on:
Blocks: 393583
  Show dependency tree
 
Reported: 2012-04-07 20:35 UTC by Dan Dexter
Modified: 2012-04-28 17:44 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
emerge --info (emerge_info.txt,5.41 KB, text/plain)
2012-04-07 20:36 UTC, Dan Dexter 		Details
build.log (build.log,7.93 KB, text/plain)
2012-04-07 20:36 UTC, Dan Dexter 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Dexter 2012-04-07 20:35:03 UTC 
=dev-ruby/httpclient-2.2.2 fails 7 tests, all within './test/test_http-access2.rb' and with the same error:

<"1=2&3=4"> expected but was
<"3=4&1=2">.

Reproducible: Always

Steps to Reproduce:
1. FEATURES="test" USE='doc -ruby_targets_jruby -ruby_targets_ree18 ruby_targets_ruby18' emerge -1v =dev-ruby/httpclient-2.2.2

Or:
2. FEATURES="test" USE='doc ruby_targets_jruby -ruby_targets_ree18 ruby_targets_ruby18' emerge -1v =dev-ruby/httpclient-2.2.2
Comment 1 Dan Dexter 2012-04-07 20:36:08 UTC 
Created attachment 308157 [details]
emerge --info
Comment 2 Dan Dexter 2012-04-07 20:36:25 UTC 
Created attachment 308159 [details]
build.log
Comment 3 Hans de Graaff gentoo-dev Security 2012-04-08 07:11:20 UTC 
These test failures are harmless: they are caused by changes in the hash ordering in the latest dev-lang/ruby:1.8 versions.
Comment 4 Hans de Graaff gentoo-dev Security 2012-04-28 17:44:41 UTC 
This has been fixed upstream. For our current versions we will no longer run these tests since the tests are not reliable.