ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: ngotogenome@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:71504] [Ruby trunk - Bug #11697] [Open] test/dtrace failure on Solaris 10
Date: Mon, 16 Nov 2015 12:16:17 +0000	[thread overview]
Message-ID: <redmine.issue-11697.20151116121616.8654db47d4dd2004@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11697.20151116121616@ruby-lang.org

Issue #11697 has been reported by Naohisa Goto.

----------------------------------------
Bug #11697: test/dtrace failure on Solaris 10
https://bugs.ruby-lang.org/issues/11697

* Author: Naohisa Goto
* Status: Open
* Priority: Normal
* Assignee: 
* ruby -v: -
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
test/dtrace fails on Solaris 10 as follows.

Ruby (64-bit) compiled by using Oracle Solaris Studio 12.3 cc with "-xO3" optimization:

~~~
$ SUDO=sudo ruby test/runner.rb test/dtrace
Run options:

# Running tests:

[26/26] DTrace::TestStringProbes#test_object_create_start_string_lit = 1.5
  1) Failure:
DTrace::TestStringProbes#test_object_create_start_string_lit [/XXXXX-52420/test/dtrace/test_string.rb:10]:
<["String"]> expected but was
<[]>.

Finished tests in 33.513504s, 0.7758 tests/s, 6.2960 assertions/s.
26 tests, 211 assertions, 1 failures, 0 errors, 0 skips

ruby -v: ruby 2.3.0dev (2015-11-01) [sparc64-solaris2.10]
~~~

Ruby (64-bit) compiled by using Solaris Studio 12.3 cc without optimization (with "-xO0") :

~~~
$ SUDO=sudo ruby test/runner.rb test/dtrace
Run options: 

# Running tests:

[ 3/26] DTrace::TestCMethod#test_entry = 1.77 s                  
  1) Failure:
DTrace::TestCMethod#test_entry [/XXXXX-52250/test/dtrace/test_cmethod.rb:18]:
<1> expected but was
<0>.

Finished tests in 40.703063s, 0.6388 tests/s, 5.2330 assertions/s.                   
26 tests, 213 assertions, 1 failures, 0 errors, 0 skips

ruby -v: ruby 2.3.0dev (2015-10-24) [sparc64-solaris2.10]
~~~

It seems that the failure is due to overflowing of dtrace's trace buffer.
On Solaris, the default buffer size is 4MB.
The failure does not happen when increasing the buffer size to 8MB (calling dtrace with "-b 8m" option)

~~~
--- test/dtrace/helper.rb.ORIG~ 2014-11-19 23:15:23.909272000 +0900
+++ test/dtrace/helper.rb       2015-11-16 21:03:35.411936000 +0900
@@ -26,7 +26,7 @@
       d_path  = d.path
       rb_path = rb.path
 
-      cmd = ["dtrace", "-q", "-s", d_path, "-c", "#{EnvUtil.rubybin} -I#{INCLUDE} #{rb_path}"]
+      cmd = ["dtrace", "-b", "8m", "-q", "-s", d_path, "-c", "#{EnvUtil.rubybin} -I#{INCLUDE} #{rb_path}"]
       if sudo = @@sudo
         [RbConfig::CONFIG["LIBPATHENV"], "RUBY", "RUBYOPT"].each do |name|
           if name and val = ENV[name]
~~~





-- 
https://bugs.ruby-lang.org/

           reply	other threads:[~2015-11-16 11:46 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <redmine.issue-11697.20151116121616@ruby-lang.org>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.issue-11697.20151116121616.8654db47d4dd2004@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).