From: SASADA Koichi <ko1@...>
Date: 2008-01-03T17:55:47+09:00
Subject: bug reports about 1.9 VM

Hi,

I'm sorry but I can't check ruby-core frequently (and ruby-talk,
it's too hard to catch up for me).  So if you have any important
issue around 1.9 VM, please post it with CC to me.


Or if you have ruby commit account, please add a test (*).  I can't
forget it :)


(*) How to use bootstraptest/test_knwonbug.rb

You can add assertions to bootstraptest/test_knownbug.rb.  It's
similar to test/unit assertion but tanaka-san and someone expand
these methods.  One important difference between test/unit is that
tests run in separated process, and you should pass test program in
string.  You can put any tests cause SEGV tests, hung-up tests or
breaking ruby's environment tests (such as remove all methods or
so).  Messages placed at last argument is important for tracing a bug.

These tests are executed by "make test" or you can run it directly
with following command-line.

  $ driver-ruby bootstraptest/runner.rb --ruby=target-ruby

You can run bootstrapruby/runner.rb with ruby 1.8.  It's means that
you can run these tests for any ruby implementation that you want to
implement 1.9 features.  And you can check minimum tests for CRuby
1.9 with drastic changes which can't run test/unit (yes, this
feature is for me :)).

a) regular test

  assert_equal(expect-string, ruby-script, message)

  ex)
  assert_equal "2", %q( 1 + 1 ), "[ruby-core:xxx] reported by Foo"

b) check core dumps

  assert_normal_exit(ruby-script, message)

  ex)
  assert_normal_exit %q{
    program something to cause SEGV.
  }, '[ruby-dev:xxx] reported by Akira Tanaka'

c) check hung-up

  assert_finish(second-to-wait, ruby-script, message)

  ex)
  assert_finish(10, %q{
    program that should finish in 10 seconds
  }, '[ruby-core:xxx] reported by Foo'

d) others

  There are more assertion methods.  Please read
  bootstraptest/runner.rb for more details.


Regards,
-- 
// SASADA Koichi at atdot dot net