Publisher2 should not set SubscribedToIMyEvent

When_multi_subscribing_to_a_polymorphic_event was running into a timing issue in the build server hence the reason to randomly fail.
The diagnostics added were very helpful, thanks @andreasohlund.
Here is what the diagnostics showed:
Trace:
02:23:54.058200 - Subscriber1 subscribing to both events
02:23:55.677200 - Publisher2 OnEndpointSubscribed NServiceBus.AcceptanceTests.PubSub.When_multi_subscribing_to_a_polymorphic_event+MyEvent2, NServiceBus.AcceptanceTests, Version=0.0.0.0, Culture=neutral, PublicKeyToken=9fc386479f8a226c
02:23:55.749200 - Publisher2 OnEndpointSubscribed NServiceBus.AcceptanceTests.PubSub.When_multi_subscribing_to_a_polymorphic_event+IMyEvent, NServiceBus.AcceptanceTests, Version=0.0.0.0, Culture=neutral, PublicKeyToken=9fc386479f8a226c
02:23:55.759200 - Publishing MyEvent2
02:23:55.763200 - Publishing MyEvent1
02:23:55.936200 - Subscribers for MyEvent2 : PubSub.Subscriber1.WhenMultiSubscribingToAPolymorphicEvent.Msmq@AMAZONA-8QQ0TT5
02:23:56.765200 - Publisher1 OnEndpointSubscribed NServiceBus.AcceptanceTests.PubSub.When_multi_subscribing_to_a_polymorphic_event+IMyEvent, NServiceBus.AcceptanceTests, Version=0.0.0.0, Culture=neutral, PublicKeyToken=9fc386479f8a226c
02:23:57.072200 - Got event 'NServiceBus.AcceptanceTests.PubSub.When_multi_subscribing_to_a_polymorphic_event+MyEvent2'

So it looks like Publisher2 was setting the SubscribedToIMyEvent to true before Publisher1 even received the subscription message and that caused the publishing to occur too early.
Still IMO the test look a bit weird, shouldn't we be subscribing to both MyEvent1 and MyEvent2 ?