Dear Pharoers,
I encountered a DNU when I ran all tests in a new Pharo 6.1 image created with PharoLauncher 1.0.1 on macOS Sierra 10.12.6. Should this work or is it a known issue? What is the Pharo’s policy concerning SUnit tests for stable releases? Cheers, Bernhard CompiledMethod(Object)>>doesNotUnderstand: #isMetaSide [ :rgMethod | | interestedClassName interestedClass | interestedClassName := anAnnouncement oldName. interestedClass := anAnnouncement classRenamed. rgMethod isMetaSide ifTrue: [ interestedClassName := interestedClassName , ' class'. interestedClass := interestedClass theMetaClass ]. rgMethod parentName = interestedClassName ifTrue: [ (interestedClass >> rgMethod selector) asFullRingDefinition ] ifFalse: [ rgMethod ] ] in MessageBrowser>>handleClassRenamed: in Block: [ :rgMethod | ... OrderedCollection>>collect: MessageBrowser>>handleClassRenamed: [ self handleClassRenamed: anAnnouncement ] in MessageBrowser>>classRenamed: in Block: [ self handleClassRenamed: anAnnouncement ] WorldState>>runStepMethodsIn: WorldMorph>>runStepMethods WorldState>>doOneCycleNowFor: WorldMorph>>doOneCycleNow SystemProgressMorph>>refresh SystemProgressMorph>>update: MorphChanged>>deliverTo: SystemProgressMorph(Morph)>>handleUpdate: MessageSend>>value: MessageSend>>cull: MessageSend>>cull:cull: [ action cull: anAnnouncement cull: announcer ] in AnnouncementSubscription>>deliver: in Block: [ action cull: anAnnouncement cull: announcer ] BlockClosure>>on:do: BlockClosure>>on:fork: AnnouncementSubscription>>deliver: [ "Ensure delivery to remaining announcements" subscription deliver: anAnnouncement ] in SubscriptionRegistry>>deliver:to:startingAt: in Block: [ "Ensure delivery to remaining announcements" sub...etc... BlockClosure>>ifCurtailed: SubscriptionRegistry>>deliver:to:startingAt: SubscriptionRegistry>>deliver:to: SubscriptionRegistry>>deliver: Announcer>>announce: JobProgressMorph(Morph)>>doAnnounce: JobProgressMorph(Morph)>>changed: JobProgressMorph>>label: SystemProgressMorph class>>updateJob: |
Hi,
We have a new bug that got introduced by some changed done in between 6.0 and 6.1. I have not yet found the cause. It would be nice to fix it as it for now makes very CI test run fail. Marcus
|
Free forum by Nabble | Edit this page |