Bill, I guess I missed the Metacello stack and I can't seem to find it... if you could point me to the post with your Metacello stack in it I will be glad to take a loook.
Dale ----- Original Message ----- | From: "Wilhelm K Schwab" <[email protected]> | To: [email protected] | Sent: Friday, February 10, 2012 2:21:30 AM | Subject: Re: [Pharo-project] 1.4 - better from Jenkins | | 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? | | As for "continuing beyond errors" - AFAIK, *I* am not saving the | image in a confused state, but *something* appears to be doing just | that. Yes, I "ignored errors" in the sense that I used the task | manager to kill off an image that was flailing trying to download | packages, and was mystified to discover that, without an explicit | save on my part, the image "woke up" trying to do the same fruitless | exercise. Several iterations of trying to unravel that led to the | large log. I then removed the log, did one cycle, and posted the | log from that. | | Bill | | | | | ________________________________________ | From: [email protected] | [[email protected]] on behalf of Dale | Henrichs [[email protected]] | Sent: Thursday, February 09, 2012 8:33 PM | To: [email protected] | Subject: Re: [Pharo-project] 1.4 - better from Jenkins | | Bill, | | The last time you complained about Metacello being broken I asked you | for a stack trace and I have seen no stack trace, although I believe | that you were able to confirm that Metacello worked fine until you | loaded some of your own code into the system ... | | Here you are complaining again ... if you don't provide specifics, | the issues cannot be resolved ... | | There are apparently a lot of moving parts in your system, so it | takes great attention to detail to get such a system running | smoothly. The fact that you don't provide specifics tells me that | perhaps you are not paying attention to the details ... | | When you are porting to a new environment (for you) like Pharo 1.4, | you should stop and isolate the FIRST ERROR that you encounter ... | in a complicated system once an error occurs, all bets are off ... | You MUST pay attention to details ... | | You state that you have a giant debug log ... so it sounds like you | tried to keep moving forward in the face of initial errors...I say | good luck with that approach! | | If you post a Metacello stack trace I can very likely tell you what | went wrong, if you prefer to continue to whine and complain about | Metacello without even attempting to help me characterize the | issues, then I will leave you to your own devices and you can can | complain about Metacello all you want --- I won't be paying | attention any more:) | | Dale | | | ----- Original Message ----- | | From: "Wilhelm K Schwab" <[email protected]> | | To: [email protected] | | Sent: Thursday, February 9, 2012 4:26:27 PM | | Subject: Re: [Pharo-project] 1.4 - better from Jenkins | | | | I think you might be right about loading the .mcz files. But I | | don't | | have an expectation other than what has been said here many times: | | that Metacello is the future. So far, I don't see it. | | | | Bill | | | | | | ________________________________________ | | From: [email protected] | | [[email protected]] on behalf of Yanni | | Chiu [[email protected]] | | Sent: Thursday, February 09, 2012 6:22 PM | | To: [email protected] | | Subject: Re: [Pharo-project] 1.4 - better from Jenkins | | | | On 09/02/12 5:39 PM, Schwab,Wilhelm K wrote: | | > Sven, | | > | | > Fair enough, but the game plan is for people to use Metacello | | > configurations to load what they need to build an image. I am | | > attempting to do just that, and am reporting (rather negative so | | > far) experience, with debug logs. | | > | | > Pharo's fault or not, something is broken. But if Pharo is going | | > to send users into the current state of Metacello, the weather | | > around the lighthouse is going to be grim. | | > | | > Interesting ideas about the package cache being damaged. Maybe | | > the | | > logs will reveal something?? | | | | You might want to check the package cache for 0-length .mcz files, | | which | | might happen when the server is down. | | | | When I upgrade to a new image version, I just start my build | | process | | with the new image, and cross my fingers. If it fails, then I do it | | manually with the build script in a workspace - select each | | framework/package and "doIt". Sometimes I run the framework's | | tests, | | after each step. | | | | I load all "community" code first, unless I have extensions to this | | code. Sometimes I've had to upgrade to a newer version of the | | framework, | | if available. At other times, I had to create patches because I was | | tracking the Pharo updates (so no fixed version was available yet). | | | | In extreme cases, I've had to generate the list of packages that | | Metacello would load, then load each .mcz individually. | | | | Typically, I'd do "save image as" at various points, to be able to | | get | | back to the problem code, more quickly. | | | | I think you're pretty much following a similar process, except the | | expectation that a Metacello configuration should just load without | | problems on Pharo1.4-unstable is too optimistic. | | | | | | | | | | |
