Hi!
In a new Moose image, we cannot do a "Transcript open”. Apparently, #Transcript is bound to a NonInteractiveTranscript. NonInteractiveTranscript open raises en error. That is odd. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
I got the same in the latest Moose today, but thought that it was my local fault. +1 Cheers, Alex On Mon, Mar 21, 2016 at 8:16 PM, Alexandre Bergel <[hidden email]> wrote: Hi! _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
In reply to this post by abergel
Le 21/03/2016 20:16, Alexandre Bergel a écrit :
> Hi! > > In a new Moose image, we cannot do a "Transcript open”. Apparently, #Transcript is bound to a NonInteractiveTranscript. > NonInteractiveTranscript open raises en error. > > That is odd. > > Cheers, > Alexandre > days… A temporary workaround is to execute "ThreadSakeTranscript install". -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev signature.asc (836 bytes) Download Attachment |
On 21/03/2016 21:24, Cyril Ferlicot D. wrote: > > This was introduced by Pharo 5 but should have been corrected since few > days… A temporary workaround is to execute "ThreadSakeTranscript install". > I saw that the Moose 6 build did not succeed the past few days, so the last green version is the one with the bug in Pharo. As soon as another image will be green for Moose6, the bug will vanish. -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev signature.asc (817 bytes) Download Attachment |
Okay. Thanks Cyril for looking into this
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
I fixed the build.
Doru > On Mar 22, 2016, at 6:24 PM, Alexandre Bergel <[hidden email]> wrote: > > Okay. Thanks Cyril for looking into this > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Mar 22, 2016, at 6:57 AM, Cyril Ferlicot Delbecque <[hidden email]> wrote: >> >> >> >> On 21/03/2016 21:24, Cyril Ferlicot D. wrote: >>> >>> This was introduced by Pharo 5 but should have been corrected since few >>> days… A temporary workaround is to execute "ThreadSakeTranscript install". >>> >> >> I saw that the Moose 6 build did not succeed the past few days, so the >> last green version is the one with the bug in Pharo. As soon as another >> image will be green for Moose6, the bug will vanish. >> >> -- >> Cyril Ferlicot >> >> http://www.synectique.eu >> >> 165 Avenue Bretagne >> Lille 59000 France >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com "Every thing should have the right to be different." _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
Free forum by Nabble | Edit this page |