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