I'm pushing the delayPArttwo now and after I will do that SharedQueue>>#findFirst: On Apr 21, 2009, at 11:32 AM, Nicolas Cellier wrote:
> Yes, SharedQueue>>#findFirst: MUST be corrected ASAP > > 2009/4/21 Stéphane Ducasse <[email protected]>: >> So nicolas should I harvest the find related bug fixes? >> >> >> On Apr 20, 2009, at 10:34 PM, Nicolas Cellier wrote: >> >>> Wait, I think the problem is not at all caused by Concurrency >>> fixes... >>> >>> I strongly suspect introduction of SharedQueue>>#findFirst: >>> >>> The test hang randomly in: >>> >>> InputEventSensor>>peekKeyboardEvent >>> "Allows for use of old Sensor protocol to get at the keyboard, >>> as when running kbdTest or the InterpreterSimulator in >>> Morphic" >>> >>> ^eventQueue findFirst: [:buf | self isKbdEvent: buf] >>> >>> Old code was: >>> >>> peekKeyboardEvent >>> "Return the next keyboard char event from the receiver or >>> nil if none >>> available" >>> ^eventQueue nextOrNilSuchThat: >>> [:buf | >>> buf first = >>> EventTypeKeyboard and: [(buf fourth) = EventKeyChar]] >>> >>> But I noticed SharedQueue>>findFirst: and >>> SharedQueue>>nextOrNilSuchThat: are not EXACTLY the same... >>> findFirst: FAILS TO INCREMENT readPos... >>> >>> >>> Nicolas >>> >>> >>> 2009/4/20 Stéphane Ducasse <[email protected]>: >>>> I know that john has a vm with traces but I do not know how to do >>>> what >>>> you need. >>>> Do you think that it can help if I integrate the next batch? >>>> Nicolas I can also remove from the stream the item so that you can >>>> take time to look at it. >>>> you just need to load the version 836 of the scriptLoader (from the >>>> pharo repository). >>>> and manually launch the loading of the last update. >>>> >>>> ScriptLoader new update10287 >>>> >>>> Stef >>>> >>>> On Apr 20, 2009, at 10:15 PM, Nicolas Cellier wrote: >>>> >>>>> Do you know how to dump Smalltalk process stacks from within the >>>>> VM >>>>> debugger (I mean gdb) ? >>>>> >>>>> 2009/4/20 Nicolas Cellier <[email protected]>: >>>>>> But the tests just blocked after 2256 run, 2162 passes, etc... >>>>>> and no response to ALT+. :( >>>>>> >>>>>> I will have a quick look... >>>>>> >>>>>> 2009/4/20 Stéphane Ducasse <[email protected]>: >>>>>>> Ok now I understand why I only got 14 and not 16 tests green. >>>>>>> >>>>>>> >>>>>>> On Apr 20, 2009, at 9:54 PM, Nicolas Cellier wrote: >>>>>>> >>>>>>>> Yes, it seems OK >>>>>>>> The tests are running on my linux versions now... not yet >>>>>>>> frozen >>>>>>>> The two additionnal DelayTest from Andreas which were in >>>>>>>> KernelTests-nice.95.mcz are not yet loaded but will be with >>>>>>>> KernelTests-nice.96.mcz >>>>>>>> >>>>>>>> Nicolas >>>>>>>> >>>>>>>> 2009/4/20 Stéphane Ducasse <[email protected]>: >>>>>>>>> it is not a problem. >>>>>>>>> I just want to make sure. Some changes are easy to undo some >>>>>>>>> not. >>>>>>>>> So I will integrate the second batch. >>>>>>>>> Did you have a look at the integration I just did. >>>>>>>>> >>>>>>>>> Stef >>>>>>>>> >>>>>>>>> On Apr 20, 2009, at 9:42 PM, Nicolas Cellier wrote: >>>>>>>>> >>>>>>>>>> Yes, >>>>>>>>>> Kernel-nice.renggli.301.mcz simply remove the upper limit for >>>>>>>>>> Delay >>>>>>>>>> because Andreas changes solved the problem. >>>>>>>>>> KernelTests-nice.96.mcz change the Delay upper bound test >>>>>>>>>> System-Support-nice.11.mcz fix a problem of sending >>>>>>>>>> deprecated >>>>>>>>>> Process>>#offList (it should have gone with earlier change) >>>>>>>>>> >>>>>>>>>> I wanted to decompose integration of Andreas changes >>>>>>>>>> carefully >>>>>>>>>> to be >>>>>>>>>> sure it can be redone... >>>>>>>>>> But now, I realize that I published too many messages, that's >>>>>>>>>> confusing >>>>>>>>>> >>>>>>>>>> 2009/4/20 Stéphane Ducasse <[email protected]>: >>>>>>>>>>> >>>>>>>>>>> nicolas >>>>>>>>>>> >>>>>>>>>>> I integrated in 10287 >>>>>>>>>>> >>>>>>>>>>>>> script363 >>>>>>>>>>>>> Delay startTimerEventLoop. >>>>>>>>>>>>> (self buildConfigurationMapFor: >>>>>>>>>>>>> #('Kernel-nice.renggli.300.mcz')) load >>>>>>>>>>> >>>>>>>>>>> So I imagine that the following one is another fix that I >>>>>>>>>>> should >>>>>>>>>>> integrate. >>>>>>>>>>> Is is correct >>>>>>>>>>> >>>>>>>>>>>> Comment #1 on issue 688 by nicolas.cellier.aka.nice: Kernel >>>>>>>>>>>> concurrency fixes? 3.10 >>>>>>>>>>>> http://code.google.com/p/pharo/issues/detail?id=688 >>>>>>>>>>>> >>>>>>>>>>>> I published the changes in PharoInbox >>>>>>>>>>>> I checked that entire changes related to mantis 7321 list >>>>>>>>>>>> can >>>>>>>>>>>> be >>>>>>>>>>>> loaded with following instructions: >>>>>>>>>>>> >>>>>>>>>>>> Delay startTimerEventLoop. >>>>>>>>>>>> (ScriptLoader new buildConfigurationMapFor: >>>>>>>>>>>> #('Kernel-nice.renggli.301.mcz' >>>>>>>>>>>> 'KernelTests-nice.96.mcz' >>>>>>>>>>>> 'System-Support-nice.11.mcz')) load. >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> You received this message because you are listed in the >>>>>>>>>>>> owner >>>>>>>>>>>> or CC fields of this issue, or because you starred this >>>>>>>>>>>> issue. >>>>>>>>>>>> You may adjust your issue notification preferences at: >>>>>>>>>>>> http://code.google.com/hosting/settings >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Pharo-project mailing list >>>>>>>>>>> [email protected] >>>>>>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Pharo-project mailing list >>>>>>>>>> [email protected] >>>>>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Pharo-project mailing list >>>>>>>>> [email protected] >>>>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>>>>>> project >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Pharo-project mailing list >>>>>>>> [email protected] >>>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Pharo-project mailing list >>>>>>> [email protected] >>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>>>> project >>>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> [email protected] >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>> project >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [email protected] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [email protected] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
