IronRuby on Mono test log

Ruby IronRuby
1

I uploaded test log for IronRuby on Mono, specifically output of “rake
test_compiler mono=1”.

http://sparcs.kaist.ac.kr/~tinuviel/download/IronRuby/test_compiler.log

Following scenarios fail; others pass:
Scenario_RubyReturnValues2
Scenario_RubyReturnValues3
Scenario_RubyReturnValues4

2

2007/11/18, Sanghyeon S. [email protected]:

Following scenarios fail; others pass:
Scenario_RubyReturnValues2
Scenario_RubyReturnValues3
Scenario_RubyReturnValues4

These failures are bogus. Tests rely on dictionary ordering. “1 => 2,
3 => 4” prints as “3421” on Mono.

Please fix.

3

Here’s specs run.

http://sparcs.kaist.ac.kr/~tinuviel/download/IronRuby/specs.log

Note that I used MONO_IOMAP=case to avoid case sensitivity problems.
This is a good interim workaround.

4

Sanghyeon S.:?

Here’s specs run.

http://sparcs.kaist.ac.kr/~tinuviel/download/IronRuby/specs.log

Note that I used MONO_IOMAP=case to avoid case sensitivity problems.
This is a good interim workaround.

Thanks for the bug report. I forgot to include this in our release
notes.

  1. Spec stack trace reporting is broken in this release. The specs run
    (as you can see by the log, but there’s something busted in the
    reporting - we’ll investigate).

  2. Local variables are broken in the console only - they work fine in
    your programs. This is by design as the next major work item on our
    plate is to fix hosting in DLR, which will fix hosting in IronRuby,
    which will enable eval* to work.

Thanks,
-John

5

Sanghyeon S.:

Following scenarios fail; others pass:
Scenario_RubyReturnValues2
Scenario_RubyReturnValues3
Scenario_RubyReturnValues4

These failures are bogus. Tests rely on dictionary ordering. “1 => 2,
3 => 4” prints as “3421” on Mono.

Will do. Thanks for the bugrep.

-John