Hi,
just wanted to share this story of a Windows problem + possible cause so others
could be aware:
As Pablo announced a new VM version this week I used the VMManager within
PharoLauncher to update the VM executables.
Unfortunately afterwards several things got broken:
When I started a fresh
Ah may be what happened to me
Phil
On Wed, 4 Mar 2020, 19:52 Torsten Bergmann, wrote:
> Hi,
>
> just wanted to share this story of a Windows problem + possible cause so
> others could be aware:
>
>
> As Pablo announced a new VM version this week I used the VMManager within
> PharoLauncher
Thanks for your analysis.
> On 4 Mar 2020, at 19:51, Torsten Bergmann wrote:
>
> Hi,
>
> just wanted to share this story of a Windows problem + possible cause so
> others could be aware:
>
>
> As Pablo announced a new VM version this week I used the VMManager within
> PharoLauncher to
There is a new Pharo build available!
The status of the build #130 was: FAILURE.
The Pull Request #5846 was integrated: "CircularMemoryLogger is missing
#basicRecordings:"
Pull request url: https://github.com/pharo-project/pharo/pull/5846
Issue Url:
There is a new Pharo build available!
The status of the build #128 was: FAILURE.
The Pull Request #5809 was integrated: "SequenceableCollection - Add executable
comments for sorting protocol"
Pull request url: https://github.com/pharo-project/pharo/pull/5809
Issue Url:
There is a new Pharo build available!
The status of the build #129 was: FAILURE.
The Pull Request #5831 was integrated: "ReadStream optimization for #upToAll:"
Pull request url: https://github.com/pharo-project/pharo/pull/5831
Issue Url:
