Re: [Pharo-project] 1.4 - better from Jenkins
On Feb 10, 2012, at 11:22 AM, Schwab,Wilhelm K wrote:
Dale,
I'm not "complaining," I'm stating facts and asking for advice. Not only did I state that I produced a "big" debug log, I also POSTED a smaller one. If you mean something different by a "stack trace," can you provide some instructions for how to obtain it?
What we need is a description of how to re-produce the problem. Do not think that anyone can (or even wants to help) if you just say "I did something and than I got strange results". Make it reproducable, and then add a bug report. Marcus -- Marcus Denker -- http://marcusdenker.de
That's precisely what I'm trying to do. Sig's answer might provide a piece of the puzzle, but I still have to figure out whether/why/how the problem really does persist after executing code and not saving the image. I added some snapshots thinking I could take success as it comes and repeat steps that failure, but I removed them all (I think) when I started to discover that once hobbled, the image remains hobbled, saved or not. Weird. For all I know, I have made this reproducible. One response said essentially, "yeah, I sometimes just load the packages MC would load" - hardly the way one speaks of a robust infrastructure. ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Marcus Denker [marcus.denker@inria.fr] Sent: Friday, February 10, 2012 5:26 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.4 - better from Jenkins On Feb 10, 2012, at 11:22 AM, Schwab,Wilhelm K wrote:
Dale,
I'm not "complaining," I'm stating facts and asking for advice. Not only did I state that I produced a "big" debug log, I also POSTED a smaller one. If you mean something different by a "stack trace," can you provide some instructions for how to obtain it?
What we need is a description of how to re-produce the problem. Do not think that anyone can (or even wants to help) if you just say "I did something and than I got strange results". Make it reproducable, and then add a bug report. Marcus -- Marcus Denker -- http://marcusdenker.de
Hi Bill, I've reading about your trails with Monticello/Metacello and been surprised about all the difficulties you are having. I frequently load fairly complex configurations on top of Pharo 1.3 without a problem. You can flush Monticello caches with: MCMethodDefinition cachedDefinitions removeAll. MCFileBasedRepository allSubInstancesDo: [:ea | ea flushCache]. and try removing the 'package-cache' folder from the folder containing your image. other than that, as others have said if you can isolate the problem we stand a chance of helping you Nick
On 10 February 2012 11:33, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:
That's precisely what I'm trying to do. Â Sig's answer might provide a piece of the puzzle, but I still have to figure out whether/why/how the problem really does persist after executing code and not saving the image. Â I added some snapshots thinking I could take success as it comes and repeat steps that failure, but I removed them all (I think) when I started to discover that once hobbled, the image remains hobbled, saved or not. Â Weird.
yes, the problem is when you have an error and i had wrong idea to suspend a process before scheduling request to open debugger on it :)
For all I know, I have made this reproducible. Â One response said essentially, "yeah, I sometimes just load the packages MC would load" - hardly the way one speaks of a robust infrastructure.
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Marcus Denker [marcus.denker@inria.fr] Sent: Friday, February 10, 2012 5:26 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.4 - better from Jenkins
On Feb 10, 2012, at 11:22 AM, Schwab,Wilhelm K wrote:
Dale,
I'm not "complaining," I'm stating facts and asking for advice. Â Not only did I state that I produced a "big" debug log, I also POSTED a smaller one. Â If you mean something different by a "stack trace," can you provide some instructions for how to obtain it?
What we need is a description of how to re-produce the problem. Do not think that anyone can (or even wants to help) if you just say "I did something and than I got strange results".
Make it reproducable, and then add a bug report.
    Marcus
-- Marcus Denker -- http://marcusdenker.de
-- Best regards, Igor Stasenko.
On Feb 10, 2012, at 12:18 PM, Igor Stasenko wrote:
On 10 February 2012 11:33, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:
That's precisely what I'm trying to do. Sig's answer might provide a piece of the puzzle, but I still have to figure out whether/why/how the problem really does persist after executing code and not saving the image. I added some snapshots thinking I could take success as it comes and repeat steps that failure, but I removed them all (I think) when I started to discover that once hobbled, the image remains hobbled, saved or not. Weird.
yes, the problem is when you have an error and i had wrong idea to suspend a process before scheduling request to open debugger on it :)
:) so igor do you have a fix? is it the rollback suggestion at the end of the issue? Stef
For all I know, I have made this reproducible. One response said essentially, "yeah, I sometimes just load the packages MC would load" - hardly the way one speaks of a robust infrastructure.
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Marcus Denker [marcus.denker@inria.fr] Sent: Friday, February 10, 2012 5:26 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.4 - better from Jenkins
On Feb 10, 2012, at 11:22 AM, Schwab,Wilhelm K wrote:
Dale,
I'm not "complaining," I'm stating facts and asking for advice. Not only did I state that I produced a "big" debug log, I also POSTED a smaller one. If you mean something different by a "stack trace," can you provide some instructions for how to obtain it?
What we need is a description of how to re-produce the problem. Do not think that anyone can (or even wants to help) if you just say "I did something and than I got strange results".
Make it reproducable, and then add a bug report.
Marcus
-- Marcus Denker -- http://marcusdenker.de
-- Best regards, Igor Stasenko.
On 10/02/12 5:33 AM, Schwab,Wilhelm K wrote:
For all I know, I have made this reproducible.
I must have missed the steps to reproduce it. Can you repeat them: - what Pharo-1.4 image are you starting from? - what doIt's are you executing, up to the point you see a problem?
One response said essentially, "yeah, I sometimes just load the packages MC would load" - hardly the way one speaks of a robust infrastructure.
If you're loading configurations into Pharo-1.4-unstable, you're doing a porting task. Pharo1.4 is under development and is a work in progress. It's quite possible that a package you're trying to load does not work on the particular Pharo-1.4-unstable you're using. This says nothing about "robust infrastructure". When I said to load the MC packages individually, that was the process you might need to follow to debug a problem with that package on Pharo-1.4-unstable.
participants (6)
-
Igor Stasenko -
Marcus Denker -
Nick Ager -
Schwab,Wilhelm K -
Stéphane Ducasse -
Yanni Chiu