Fwd: Metacello issues on Pharo 2.0

[Christophe Demarey]

Début du message réexpédié :

De : Christophe Demarey <Christoph...@inria.fr>

Date : 15 février 2013 15:09:27 HNEC

À : meta...@googlegroups.com

Cc : Pharo-...@lists.gforge.inria.fr

Objet : Metacello issues on Pharo 2.0

Hi all,

I have issues with Metacello on Pharo 2.0

If I load and run tests for the version used in Pharo1.4, it gives:

(ConfigurationOfMetacello project version: '1.0-beta.31.1.4') load: 'Tests'

Metacello packages shipped with Pharo 2.0 are all packages derived from the latest stable Metacello baseline (1.0-beta.31.1.5) except the MetacelloToolBox.

If I load and run tests packages with version described in the latest stable Metacello baseline (1.0-beta.31.1.5), i.e. :

• Metacello-TestsCore-DaleHenrichs.14 and
• Metacello-TestsMC-dkh.351,

it gives (Pharo 2.0 #20547):

So, it seems there are some problems. Do we use the rigth versions of Metacello packages?

Regards,

Christophe.

[Dale Henrichs]

Christophe,

I'm not exactly sure what your problem is ...

I have to admit that I haven't kept up with Pharo2.0 since last summer when I couldn't use Pharo2.0 for development because of OsProcess issues. I know that recently those issues have been cleared up, but I haven't had the time to return to Pharo2.0 and check things out (I'm facing more issues with getting PHaro2.0 to work with travis-ci, etc. so it will be a big undertaking for me to fully support Pharo2.0).

I've got a fairly recent Pharo2.0 image and it looks like there are pharo-specific versions for each of the packages loaded into Pharo2.0. I assume that the tests are all passing with those versions, although I can't say whether or not the tests had to be modified to pass in Pharo2.0 as well ... which is likely to be a source of one of the problems you are looking at ...

I don't know where the configuration exists that is being used to manage the changes for Pharo2.0 and the tests, but that is probably a good starting point ... if you are not using the proper Pharo2.0 configuration, you won't be getting the proper packages loaded ...

Dale

----- Original Message -----
| From: "Christophe Demarey" <Christoph...@inria.fr>
| To: meta...@googlegroups.com
| Cc: Pharo-...@lists.gforge.inria.fr
| Sent: Friday, February 15, 2013 6:09:27 AM
| Subject: [Pharo-project] Metacello issues on Pharo 2.0
|
| Hi all,
|
| I have issues with Metacello on Pharo 2.0
|
| If I load and run tests for the version used in Pharo1.4, it gives:
| (ConfigurationOfMetacello project version: '1.0-beta.31.1.4') load: 'Tests'
|
|
|

| Metacello packages shipped with Pharo 2.0 are all packages derived from the
| latest stable Metacello baseline (1.0-beta.31.1.5) except the
| MetacelloToolBox.
| If I load and run tests packages with version described in the latest stable
| Metacello baseline (1.0-beta.31.1.5), i.e. :
| Metacello-TestsCore-DaleHenrichs.14 and
| Metacello-TestsMC-dkh.351,
| it gives (Pharo 2.0 #20547):
|
|

| So, it seems there are some problems. Do we use the rigth versions of
| Metacello packages?
|
| Regards,
| Christophe.
|
|
|

Chr

[Dale Henrichs]

Stef,

I definitely intend to keep supporting Metacello on ALL platforms ...

I have not made any public changes to Metacello since the summer (roughly) so in one sense I've been ignoring all platforms equally for a while now ...

I am looking forward to porting the Metacello Scripting API work to Pharo2.0, but I have a number of balls in the air at them moment ...

From reading subsequent emails, it sounds as though the bar is a lot lower than it was before ... it sounds like it won't be as big a job to get things running on Pharo2.0 as I anticipated, but I still need to find some time just to get my development environment (FileTree, git/github, travisCI) operational on Pharo2.0 ...

Dale

----- Original Message -----

| From: "Stéphane Ducasse" <stephane...@inria.fr>
| To: Pharo-...@lists.gforge.inria.fr
| Cc: meta...@googlegroups.com
| Sent: Wednesday, February 20, 2013 10:14:33 AM
| Subject: Re: [Pharo-project] Metacello issues on Pharo 2.0
|
| Dale
|
| We are investing massively on metacello so now this is important for us to
| know if you will continue
| to maintain it or not.
| Because if this is not the case then we will have to rethink our strategy.
|
| Stef

[Dale Henrichs]

Stef,

Sorry I didn't see your reply as the metacello group fell off the reply list (I've fallen hopelessly behind in reading the pharo dev group and haven't been able to catch up yet) ...

I'm pretty sure that in the test that use suspendAllWhile: the semantics are important and the tests depend upon the old behavior ...

I'm pretty sure that we can arrange to move this little bit of code into the platform package...

Dale

----- Original Message -----
| From: "stephane ducasse" <stephane...@free.fr>
| To: Pharo-...@lists.gforge.inria.fr
| Sent: Tuesday, February 26, 2013 7:45:32 AM
| Subject: Re: [Pharo-project] Metacello issues on Pharo 2.0
|
|

| On Feb 25, 2013, at 8:21 PM, Dale Henrichs <dhen...@vmware.com> wrote:
|
| > I think that the suspendAllWhile: call is important because a) some
| > Metacello tests are sensitive to packages getting marked dirty or other
| > events getting triggered …
|
| Christophe tried to removed them completely but there were other problems. I
| was not with him so I do not have all the info.
| What we noticed is that suspendAllWhile: is not equilavent because the events
| have been "clarified".
|
| Stef

|
| >
| >
| >
| > ----- Original Message -----
| > | From: "Christophe Demarey" <Christoph...@inria.fr>
| > | To: Pharo-...@lists.gforge.inria.fr
| > | Sent: Thursday, February 21, 2013 1:26:31 AM
| > | Subject: Re: [Pharo-project] Metacello issues on Pharo 2.0
| > |
| > | Dale
| > |

| > | we run the tests simply rewriting runCase as
| > |
| > | runCase
| > | | original |
| > | (self doSilently) ifFalse: [ ^super runCase ].
| > | original := MetacelloPlatform current bypassGoferLoadUpdateCategories.
| > | [
| > | MetacelloPlatform current bypassGoferLoadUpdateCategories: true.
| > | ^ SystemAnnouncer uniqueInstance suspendAllWhile: [ super runCase ]
| > | ensure: [ MetacelloPlatform current bypassGoferLoadUpdateCategories:
| > | original ]
| > |
| > | but it seems that we do not have the same behavior between the two
| > |
| > | runCase
| > | | original |
| > | (self doSilently) ifFalse: [ ^super runCase ].
| > | original := MetacelloPlatform current bypassGoferLoadUpdateCategories.
| > | [
| > | MetacelloPlatform current bypassGoferLoadUpdateCategories: true.
| > | ^ super runCase ]
| > | ensure: [ MetacelloPlatform current bypassGoferLoadUpdateCategories:
| > | original ]
| > |
| > | So we will run all the tests
| > |
| > | Stef
| >
|

[Dale Henrichs]

Stef,

Let me know how the swap goes ... (on the metacello list this time:)

Dale

----- Original Message -----
| From: "stephane ducasse" <stephane...@free.fr>
| To: Pharo-...@lists.gforge.inria.fr
| Sent: Tuesday, February 26, 2013 7:50:54 AM
| Subject: Re: [Pharo-project] Metacello issues on Pharo 2.0
|
| >
| > |

| > | let us know how you want that we proceed.
| >
| > I will have to look at the changes themselves to determine which direction
| > to go ... if the changes are isolated enough I'd be inclined to hide them
| > in MetacelloPlatform ... that's where the platform uglies go ... If the
| > changes are extensive, then I'd consider extracting out a
| > filedirectory[1]/filesystem[2] utilities package (as was done for zinc and
| > filetree).
|
| I have the impression when I checked all the changes that they are minor but
| impacting (FS for example)
|
|
| > [1]
| > https://github.com/dalehenrich/filetree/tree/pharo2.0/repository/MonticelloFileTree-FileDirectory-Utilities.package
| > [2]
| > https://github.com/dalehenrich/filetree/tree/pharo2.0/repository/MonticelloFileTree-FileSystem-Utilities.package
| > |
| > | - for the tests (not version 10.32 that I cannot load - I will have a
| > | look
| >
| > Metacello 1.0-beta.32 is the Metacello Preview version (not yet released
| > anywhere) and porting that version stopped me cold last summer ...
| > OSProcess was the final straw:)
|
| Ok I could not load it because ProfStef was not found but I can retry.
|
| > | at profStef to make it 2.0 aware I guess that this is that the problem)
| > | runCase refers to SystemNotifier
| > |
| > | versions accesssor => look really suspicious)
| >
| > Yeah, that looks very suspicious and tests won't pass without that puppy:)
|
| yes to me it looks really strange.
|
| >
| > | 'Metacello-TestsTutorial-dkh.33';
| > | package: 'Metacello-ToolBox' with:
| > | 'Metacello-ToolBox-dkh.130'
| > | -> Metacello-ToolBox-MarcusDenker.135
| > |
| > | here this is strange because the version of the toolbox in Pharo is
| > | based on 135 134 133 132 131 127 126 .... so should we take another
| > | version of the toolbox?
| > | May be there was a mistake from our side to take a wrong branch.
| >
| > You are on the right branch, Metacello-ToolBox-dkh.130 is okay (it's part
| > of Metacello 1.0-beta.31.1.5) but Metacello-ToolBox-dkh.131 is part of the
| > Preview release.
|
| We do not use 130 but 135 so we are using the wrong branch.
|
|
|
| So do you have idea of experience we should run.
| I think that we should try to load metacello-Toolbox.130 and check the tests
|