[Pharo-project] Continuing weirdness with SS3.gemstone.com and Monticello in Pharo 2.0
So, I wanted to merge my stuff from the SS3 project. When loading it needed to have BitBltPen (which I had somewhere as in BitBltPen-MarianoMartinezPeck.4.mcz) I wanted to put that into my SS3 area and so, added the repository to the list of repos in monticello, then took the mcz and then added the repository to the package. Net result: Frozen image. No amount of Cmd-. could do anything. See screenshot. ... now restarting VM... Phil
this is rather strange. We're using gemstone for all pharo development and we haven't had any problems with it. I loaded all the stuff from your test-repository and it worked. more details? ;) On 2013-02-19, at 22:06, "phil@highoctane.be" <phil@highoctane.be> wrote:
So, I wanted to merge my stuff from the SS3 project.
When loading it needed to have BitBltPen (which I had somewhere as in BitBltPen-MarianoMartinezPeck.4.mcz)
I wanted to put that into my SS3 area and so, added the repository to the list of repos in monticello, then took the mcz and then added the repository to the package.
Net result: Frozen image.
No amount of Cmd-. could do anything.
See screenshot.
... now restarting VM...
Phil <Capture dâécran 2013-02-19 à 22.01.46.png>
Well, that's what you get from having people using some other kind of workflow that the usual one you gurus use since years; they do click on some unforseen button combinations. But frozen it was for sure. Anyway, cannot send you any image for testing... it was frozen. This makes me wonder: isn't there any way to put a kind of non maskable kind of interrupt key in the VM that would interrupt its execution for sure? I do encounter a tad too many freezes. Some of them my fault but quite some others not really. I now understand why one would have a process saving images with an incrementing number endlessly in the background to avoid just that now. I don't even want to think about life before Monticello ... Yikes! Phil 2013/2/19 Camillo Bruni <camillobruni@gmail.com>:
this is rather strange. We're using gemstone for all pharo development and we haven't had any problems with it.
I loaded all the stuff from your test-repository and it worked. more details? ;)
On 2013-02-19, at 22:06, "phil@highoctane.be" <phil@highoctane.be> wrote:
So, I wanted to merge my stuff from the SS3 project.
When loading it needed to have BitBltPen (which I had somewhere as in BitBltPen-MarianoMartinezPeck.4.mcz)
I wanted to put that into my SS3 area and so, added the repository to the list of repos in monticello, then took the mcz and then added the repository to the package.
Net result: Frozen image.
No amount of Cmd-. could do anything.
See screenshot.
... now restarting VM...
Phil <Capture dâécran 2013-02-19 à 22.01.46.png>
On Feb 19, 2013, at 11:27 PM, "phil@highoctane.be" <phil@highoctane.be> wrote:
Well, that's what you get from having people using some other kind of workflow that the usual one you gurus use since years; they do click on some unforseen button combinations. But frozen it was for sure.
yep... and that's why your reports are welcome, we need some others than us trying the system to find this issues before release (otherwise, it will be a failed release, and no one wants that :)
Anyway, cannot send you any image for testing... it was frozen.
This makes me wonder: isn't there any way to put a kind of non maskable kind of interrupt key in the VM that would interrupt its execution for sure?
I do encounter a tad too many freezes. Some of them my fault but quite some others not really. I now understand why one would have a process saving images with an incrementing number endlessly in the background to avoid just that now.
I don't even want to think about life before Monticello ... Yikes!
tbh, I know about this problem since a couple of days: is a vm problem that we are trying to figure out if is a problem in our merge or it is a JIT problem (I think is the last one, but I have to be sure before transmit it to Eliot) Esteban
Phil
2013/2/19 Camillo Bruni <camillobruni@gmail.com>:
this is rather strange. We're using gemstone for all pharo development and we haven't had any problems with it.
I loaded all the stuff from your test-repository and it worked. more details? ;)
On 2013-02-19, at 22:06, "phil@highoctane.be" <phil@highoctane.be> wrote:
So, I wanted to merge my stuff from the SS3 project.
When loading it needed to have BitBltPen (which I had somewhere as in BitBltPen-MarianoMartinezPeck.4.mcz)
I wanted to put that into my SS3 area and so, added the repository to the list of repos in monticello, then took the mcz and then added the repository to the package.
Net result: Frozen image.
No amount of Cmd-. could do anything.
See screenshot.
... now restarting VM...
Phil <Capture dâécran 2013-02-19 à 22.01.46.png>
are you sure that this is a freeze and not a timeout on the repository? Because the timeout can take some time. Stef On Feb 19, 2013, at 11:27 PM, phil@highoctane.be wrote:
Well, that's what you get from having people using some other kind of workflow that the usual one you gurus use since years; they do click on some unforseen button combinations. But frozen it was for sure.
Anyway, cannot send you any image for testing... it was frozen.
This makes me wonder: isn't there any way to put a kind of non maskable kind of interrupt key in the VM that would interrupt its execution for sure?
I do encounter a tad too many freezes. Some of them my fault but quite some others not really. I now understand why one would have a process saving images with an incrementing number endlessly in the background to avoid just that now.
I don't even want to think about life before Monticello ... Yikes!
Phil
2013/2/19 Camillo Bruni <camillobruni@gmail.com>:
this is rather strange. We're using gemstone for all pharo development and we haven't had any problems with it.
I loaded all the stuff from your test-repository and it worked. more details? ;)
On 2013-02-19, at 22:06, "phil@highoctane.be" <phil@highoctane.be> wrote:
So, I wanted to merge my stuff from the SS3 project.
When loading it needed to have BitBltPen (which I had somewhere as in BitBltPen-MarianoMartinezPeck.4.mcz)
I wanted to put that into my SS3 area and so, added the repository to the list of repos in monticello, then took the mcz and then added the repository to the package.
Net result: Frozen image.
No amount of Cmd-. could do anything.
See screenshot.
... now restarting VM...
Phil <Capture dâécran 2013-02-19 à 22.01.46.png>
Freeze. I let the image open for more than 3 hours without any change. Phil 2013/2/20 stephane ducasse <stephane.ducasse@free.fr>:
are you sure that this is a freeze and not a timeout on the repository? Because the timeout can take some time.
Stef On Feb 19, 2013, at 11:27 PM, phil@highoctane.be wrote:
Well, that's what you get from having people using some other kind of workflow that the usual one you gurus use since years; they do click on some unforseen button combinations. But frozen it was for sure.
Anyway, cannot send you any image for testing... it was frozen.
This makes me wonder: isn't there any way to put a kind of non maskable kind of interrupt key in the VM that would interrupt its execution for sure?
I do encounter a tad too many freezes. Some of them my fault but quite some others not really. I now understand why one would have a process saving images with an incrementing number endlessly in the background to avoid just that now.
I don't even want to think about life before Monticello ... Yikes!
Phil
2013/2/19 Camillo Bruni <camillobruni@gmail.com>:
this is rather strange. We're using gemstone for all pharo development and we haven't had any problems with it.
I loaded all the stuff from your test-repository and it worked. more details? ;)
On 2013-02-19, at 22:06, "phil@highoctane.be" <phil@highoctane.be> wrote:
So, I wanted to merge my stuff from the SS3 project.
When loading it needed to have BitBltPen (which I had somewhere as in BitBltPen-MarianoMartinezPeck.4.mcz)
I wanted to put that into my SS3 area and so, added the repository to the list of repos in monticello, then took the mcz and then added the repository to the package.
Net result: Frozen image.
No amount of Cmd-. could do anything.
See screenshot.
... now restarting VM...
Phil <Capture dâécran 2013-02-19 à 22.01.46.png>
can you try on the StackVM? http://pharo.gforge.inria.fr/ci/vm/stack/ so I am convinced it is not a Pharo problem per se, but a nasty issue with the VM On 2013-02-20, at 22:01, "phil@highoctane.be" <phil@highoctane.be> wrote:
Freeze. I let the image open for more than 3 hours without any change.
Phil
2013/2/20 stephane ducasse <stephane.ducasse@free.fr>:
are you sure that this is a freeze and not a timeout on the repository? Because the timeout can take some time.
Stef On Feb 19, 2013, at 11:27 PM, phil@highoctane.be wrote:
Well, that's what you get from having people using some other kind of workflow that the usual one you gurus use since years; they do click on some unforseen button combinations. But frozen it was for sure.
Anyway, cannot send you any image for testing... it was frozen.
This makes me wonder: isn't there any way to put a kind of non maskable kind of interrupt key in the VM that would interrupt its execution for sure?
I do encounter a tad too many freezes. Some of them my fault but quite some others not really. I now understand why one would have a process saving images with an incrementing number endlessly in the background to avoid just that now.
I don't even want to think about life before Monticello ... Yikes!
Phil
2013/2/19 Camillo Bruni <camillobruni@gmail.com>:
this is rather strange. We're using gemstone for all pharo development and we haven't had any problems with it.
I loaded all the stuff from your test-repository and it worked. more details? ;)
On 2013-02-19, at 22:06, "phil@highoctane.be" <phil@highoctane.be> wrote:
So, I wanted to merge my stuff from the SS3 project.
When loading it needed to have BitBltPen (which I had somewhere as in BitBltPen-MarianoMartinezPeck.4.mcz)
I wanted to put that into my SS3 area and so, added the repository to the list of repos in monticello, then took the mcz and then added the repository to the package.
Net result: Frozen image.
No amount of Cmd-. could do anything.
See screenshot.
... now restarting VM...
Phil <Capture dâécran 2013-02-19 à 22.01.46.png>
No, I can't as 2013/2/20 Camillo Bruni <camillobruni@gmail.com>:
can you try on the StackVM?
http://pharo.gforge.inria.fr/ci/vm/stack/
so I am convinced it is not a Pharo problem per se, but a nasty issue with the VM
On 2013-02-20, at 22:01, "phil@highoctane.be" <phil@highoctane.be> wrote:
Freeze. I let the image open for more than 3 hours without any change.
Phil
2013/2/20 stephane ducasse <stephane.ducasse@free.fr>:
are you sure that this is a freeze and not a timeout on the repository? Because the timeout can take some time.
Stef On Feb 19, 2013, at 11:27 PM, phil@highoctane.be wrote:
Well, that's what you get from having people using some other kind of workflow that the usual one you gurus use since years; they do click on some unforseen button combinations. But frozen it was for sure.
Anyway, cannot send you any image for testing... it was frozen.
This makes me wonder: isn't there any way to put a kind of non maskable kind of interrupt key in the VM that would interrupt its execution for sure?
I do encounter a tad too many freezes. Some of them my fault but quite some others not really. I now understand why one would have a process saving images with an incrementing number endlessly in the background to avoid just that now.
I don't even want to think about life before Monticello ... Yikes!
Phil
2013/2/19 Camillo Bruni <camillobruni@gmail.com>:
this is rather strange. We're using gemstone for all pharo development and we haven't had any problems with it.
I loaded all the stuff from your test-repository and it worked. more details? ;)
On 2013-02-19, at 22:06, "phil@highoctane.be" <phil@highoctane.be> wrote:
So, I wanted to merge my stuff from the SS3 project.
When loading it needed to have BitBltPen (which I had somewhere as in BitBltPen-MarianoMartinezPeck.4.mcz)
I wanted to put that into my SS3 area and so, added the repository to the list of repos in monticello, then took the mcz and then added the repository to the package.
Net result: Frozen image.
No amount of Cmd-. could do anything.
See screenshot.
... now restarting VM...
Phil <Capture dâécran 2013-02-19 à 22.01.46.png>
when image freezes and not responsible anymore, VM can still respond to kill -SIGUSR1 <vm-pid> which will print the stack trace on console. this can help with determining the cause of problem. -- Best regards, Igor Stasenko.
On Thu, Feb 21, 2013 at 5:18 AM, Igor Stasenko <siguctua@gmail.com> wrote:
when image freezes and not responsible anymore, VM can still respond to
kill -SIGUSR1 <vm-pid>
Hmm, not in the Cocoa Vm :(. The process gets killed...
which will print the stack trace on console.
this can help with determining the cause of problem.
-- Best regards, Igor Stasenko.
Cmd-Alt-Esc and Pharo kill is my not so welcome friend on OSX. BTW, the VM feels speedier on Windows (XP and 7 here) than on OSX. Is there anyone experiencing this as well? Phil 2013/2/21 Guillermo Polito <guillermopolito@gmail.com>:
On Thu, Feb 21, 2013 at 5:18 AM, Igor Stasenko <siguctua@gmail.com> wrote:
when image freezes and not responsible anymore, VM can still respond to
kill -SIGUSR1 <vm-pid>
Hmm, not in the Cocoa Vm :(. The process gets killed...
which will print the stack trace on console.
this can help with determining the cause of problem.
-- Best regards, Igor Stasenko.
participants (6)
-
Camillo Bruni -
Esteban Lorenzano -
Guillermo Polito -
Igor Stasenko -
phil＠highoctane.be -
stephane ducasse