In the ClrGenerics3 scenario:
 

    public class ClassWithNestedGenericTypes1 {
        public class D {
        }

 

        public class C {
            public int Id { get { return 0; } }
        }

 

        public class C<T> {
            public int Id { get { return 1; } }
        }
    }

 
IronRuby currently assumes that it will find C before C`1 when creating the different type groups. The test fails if you simply invert the two C declarations:
 

    public class ClassWithNestedGenericTypes1 {
        public class D {
        }

 

        public class C<T> {
            public int Id { get { return 1; } }
        }

 

        public class C {
            public int Id { get { return 0; } }
        }
    }