jenkins jobs on pharo 3.0

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

jenkins jobs on pharo 3.0

Tudor Girba-2
Hi,

I reconfigured all official Moose Jenkins jobs to work with Pharo 3.0:

There still are a couple of issues with loading, but the builds do not look that bad.

Cheers,
Doru

--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: jenkins jobs on pharo 3.0

abergel
Thanks Doru for this effort!

Alexandre


On Nov 1, 2013, at 11:28 AM, Tudor Girba <[hidden email]> wrote:

> Hi,
>
> I reconfigured all official Moose Jenkins jobs to work with Pharo 3.0:
> https://ci.inria.fr/moose/view/Moose%205.0/?
>
> There still are a couple of issues with loading, but the builds do not look that bad.
>
> Cheers,
> Doru
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: jenkins jobs on pharo 3.0

Tudor Girba-2
After about half an hour of work, all jobs build.

Moose still has some 400 tests failing and Glamour a couple, but we are now in position to deal with them.

Please feel free to take a look, and use the mailing list for coordination when you start looking into something more closely.

Cheers,
Doru


On Fri, Nov 1, 2013 at 3:49 PM, Alexandre Bergel <[hidden email]> wrote:
Thanks Doru for this effort!

Alexandre


On Nov 1, 2013, at 11:28 AM, Tudor Girba <[hidden email]> wrote:

> Hi,
>
> I reconfigured all official Moose Jenkins jobs to work with Pharo 3.0:
> https://ci.inria.fr/moose/view/Moose%205.0/?
>
> There still are a couple of issues with loading, but the builds do not look that bad.
>
> Cheers,
> Doru
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: jenkins jobs on pharo 3.0

Tudor Girba-2
Ok, I brought it down to: 33 tests failing in Moose (of which 3 are Glamour).

The most important problem was induced by the (good) changes in the API of the RB visitor (visit methods are correctly called visit* instead of accept*).

Cheers,
Doru




On Fri, Nov 1, 2013 at 7:07 PM, Tudor Girba <[hidden email]> wrote:
After about half an hour of work, all jobs build.

Moose still has some 400 tests failing and Glamour a couple, but we are now in position to deal with them.

Please feel free to take a look, and use the mailing list for coordination when you start looking into something more closely.

Cheers,
Doru


On Fri, Nov 1, 2013 at 3:49 PM, Alexandre Bergel <[hidden email]> wrote:
Thanks Doru for this effort!

Alexandre


On Nov 1, 2013, at 11:28 AM, Tudor Girba <[hidden email]> wrote:

> Hi,
>
> I reconfigured all official Moose Jenkins jobs to work with Pharo 3.0:
> https://ci.inria.fr/moose/view/Moose%205.0/?
>
> There still are a couple of issues with loading, but the builds do not look that bad.
>
> Cheers,
> Doru
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: jenkins jobs on pharo 3.0

Andre Hora
Just fixed the 6 failing tests from gtoolkit related to the call to #versionImportPragmasVerifiedDefinedIn:
It is green now (but maybe a check should be done).


On Sat, Nov 2, 2013 at 12:00 AM, Tudor Girba <[hidden email]> wrote:
Ok, I brought it down to: 33 tests failing in Moose (of which 3 are Glamour).

The most important problem was induced by the (good) changes in the API of the RB visitor (visit methods are correctly called visit* instead of accept*).

Cheers,
Doru




On Fri, Nov 1, 2013 at 7:07 PM, Tudor Girba <[hidden email]> wrote:
After about half an hour of work, all jobs build.

Moose still has some 400 tests failing and Glamour a couple, but we are now in position to deal with them.

Please feel free to take a look, and use the mailing list for coordination when you start looking into something more closely.

Cheers,
Doru


On Fri, Nov 1, 2013 at 3:49 PM, Alexandre Bergel <[hidden email]> wrote:
Thanks Doru for this effort!

Alexandre


On Nov 1, 2013, at 11:28 AM, Tudor Girba <[hidden email]> wrote:

> Hi,
>
> I reconfigured all official Moose Jenkins jobs to work with Pharo 3.0:
> https://ci.inria.fr/moose/view/Moose%205.0/?
>
> There still are a couple of issues with loading, but the builds do not look that bad.
>
> Cheers,
> Doru
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev




--
Andre Hora

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: jenkins jobs on pharo 3.0

Andre Hora
Brought it down to 15 tests failing.

(The last build is red now because SH is down :|)


On Sat, Nov 2, 2013 at 12:58 AM, Andre Hora <[hidden email]> wrote:
Just fixed the 6 failing tests from gtoolkit related to the call to #versionImportPragmasVerifiedDefinedIn:
It is green now (but maybe a check should be done).


On Sat, Nov 2, 2013 at 12:00 AM, Tudor Girba <[hidden email]> wrote:
Ok, I brought it down to: 33 tests failing in Moose (of which 3 are Glamour).

The most important problem was induced by the (good) changes in the API of the RB visitor (visit methods are correctly called visit* instead of accept*).

Cheers,
Doru




On Fri, Nov 1, 2013 at 7:07 PM, Tudor Girba <[hidden email]> wrote:
After about half an hour of work, all jobs build.

Moose still has some 400 tests failing and Glamour a couple, but we are now in position to deal with them.

Please feel free to take a look, and use the mailing list for coordination when you start looking into something more closely.

Cheers,
Doru


On Fri, Nov 1, 2013 at 3:49 PM, Alexandre Bergel <[hidden email]> wrote:
Thanks Doru for this effort!

Alexandre


On Nov 1, 2013, at 11:28 AM, Tudor Girba <[hidden email]> wrote:

> Hi,
>
> I reconfigured all official Moose Jenkins jobs to work with Pharo 3.0:
> https://ci.inria.fr/moose/view/Moose%205.0/?
>
> There still are a couple of issues with loading, but the builds do not look that bad.
>
> Cheers,
> Doru
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev




--
Andre Hora



--
Andre Hora

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: jenkins jobs on pharo 3.0

Tudor Girba-2
Thank you, Andre!

Doru


On Sat, Nov 2, 2013 at 2:23 AM, Andre Hora <[hidden email]> wrote:
Brought it down to 15 tests failing.

(The last build is red now because SH is down :|)


On Sat, Nov 2, 2013 at 12:58 AM, Andre Hora <[hidden email]> wrote:
Just fixed the 6 failing tests from gtoolkit related to the call to #versionImportPragmasVerifiedDefinedIn:
It is green now (but maybe a check should be done).


On Sat, Nov 2, 2013 at 12:00 AM, Tudor Girba <[hidden email]> wrote:
Ok, I brought it down to: 33 tests failing in Moose (of which 3 are Glamour).

The most important problem was induced by the (good) changes in the API of the RB visitor (visit methods are correctly called visit* instead of accept*).

Cheers,
Doru




On Fri, Nov 1, 2013 at 7:07 PM, Tudor Girba <[hidden email]> wrote:
After about half an hour of work, all jobs build.

Moose still has some 400 tests failing and Glamour a couple, but we are now in position to deal with them.

Please feel free to take a look, and use the mailing list for coordination when you start looking into something more closely.

Cheers,
Doru


On Fri, Nov 1, 2013 at 3:49 PM, Alexandre Bergel <[hidden email]> wrote:
Thanks Doru for this effort!

Alexandre


On Nov 1, 2013, at 11:28 AM, Tudor Girba <[hidden email]> wrote:

> Hi,
>
> I reconfigured all official Moose Jenkins jobs to work with Pharo 3.0:
> https://ci.inria.fr/moose/view/Moose%205.0/?
>
> There still are a couple of issues with loading, but the builds do not look that bad.
>
> Cheers,
> Doru
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev




--
Andre Hora



--
Andre Hora

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev




--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: jenkins jobs on pharo 3.0

abergel
Hi!

I am having a look at build #28 of Moose 5.0.
There is apparently heavily broken. Debuggers cannot be open anymore. Doiting "self halt" in a workspace opens the emergency evaluator.

Hard to check what's going on with the failing tests.
Am I the only one to see this?

Cheers,
Alexandre


On Nov 2, 2013, at 4:47 AM, Tudor Girba <[hidden email]> wrote:

> Thank you, Andre!
>
> Doru
>
>
> On Sat, Nov 2, 2013 at 2:23 AM, Andre Hora <[hidden email]> wrote:
> Brought it down to 15 tests failing.
>
> (The last build is red now because SH is down :|)
>
>
> On Sat, Nov 2, 2013 at 12:58 AM, Andre Hora <[hidden email]> wrote:
> Just fixed the 6 failing tests from gtoolkit related to the call to #versionImportPragmasVerifiedDefinedIn:
> It is green now (but maybe a check should be done).
>
>
>
> On Sat, Nov 2, 2013 at 12:00 AM, Tudor Girba <[hidden email]> wrote:
> Ok, I brought it down to: 33 tests failing in Moose (of which 3 are Glamour).
>
> The most important problem was induced by the (good) changes in the API of the RB visitor (visit methods are correctly called visit* instead of accept*).
>
> Cheers,
> Doru
>
>
>
>
> On Fri, Nov 1, 2013 at 7:07 PM, Tudor Girba <[hidden email]> wrote:
> After about half an hour of work, all jobs build.
>
> Moose still has some 400 tests failing and Glamour a couple, but we are now in position to deal with them.
>
> Please feel free to take a look, and use the mailing list for coordination when you start looking into something more closely.
>
> Cheers,
> Doru
>
>
> On Fri, Nov 1, 2013 at 3:49 PM, Alexandre Bergel <[hidden email]> wrote:
> Thanks Doru for this effort!
>
> Alexandre
>
>
> On Nov 1, 2013, at 11:28 AM, Tudor Girba <[hidden email]> wrote:
>
> > Hi,
> >
> > I reconfigured all official Moose Jenkins jobs to work with Pharo 3.0:
> > https://ci.inria.fr/moose/view/Moose%205.0/?
> >
> > There still are a couple of issues with loading, but the builds do not look that bad.
> >
> > Cheers,
> > Doru
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
>
> --
> Andre Hora
>
>
>
> --
> Andre Hora
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: jenkins jobs on pharo 3.0

Tudor Girba-2
It is due to the GTInspector being incompatible with the Pharo debugger.

I opened the thread on the Pharo mailing list, and in the meantime we should not install the GTInspector. I cannot commit right now due to STHub being down, but you can fix it by reinstalling the default Spec-based inspector:

EyeInspector registerToolsOn: Smalltalk tools.

Cheers,
Doru




On Sat, Nov 2, 2013 at 12:17 PM, Alexandre Bergel <[hidden email]> wrote:
Hi!

I am having a look at build #28 of Moose 5.0.
There is apparently heavily broken. Debuggers cannot be open anymore. Doiting "self halt" in a workspace opens the emergency evaluator.

Hard to check what's going on with the failing tests.
Am I the only one to see this?

Cheers,
Alexandre


On Nov 2, 2013, at 4:47 AM, Tudor Girba <[hidden email]> wrote:

> Thank you, Andre!
>
> Doru
>
>
> On Sat, Nov 2, 2013 at 2:23 AM, Andre Hora <[hidden email]> wrote:
> Brought it down to 15 tests failing.
>
> (The last build is red now because SH is down :|)
>
>
> On Sat, Nov 2, 2013 at 12:58 AM, Andre Hora <[hidden email]> wrote:
> Just fixed the 6 failing tests from gtoolkit related to the call to #versionImportPragmasVerifiedDefinedIn:
> It is green now (but maybe a check should be done).
>
>
>
> On Sat, Nov 2, 2013 at 12:00 AM, Tudor Girba <[hidden email]> wrote:
> Ok, I brought it down to: 33 tests failing in Moose (of which 3 are Glamour).
>
> The most important problem was induced by the (good) changes in the API of the RB visitor (visit methods are correctly called visit* instead of accept*).
>
> Cheers,
> Doru
>
>
>
>
> On Fri, Nov 1, 2013 at 7:07 PM, Tudor Girba <[hidden email]> wrote:
> After about half an hour of work, all jobs build.
>
> Moose still has some 400 tests failing and Glamour a couple, but we are now in position to deal with them.
>
> Please feel free to take a look, and use the mailing list for coordination when you start looking into something more closely.
>
> Cheers,
> Doru
>
>
> On Fri, Nov 1, 2013 at 3:49 PM, Alexandre Bergel <[hidden email]> wrote:
> Thanks Doru for this effort!
>
> Alexandre
>
>
> On Nov 1, 2013, at 11:28 AM, Tudor Girba <[hidden email]> wrote:
>
> > Hi,
> >
> > I reconfigured all official Moose Jenkins jobs to work with Pharo 3.0:
> > https://ci.inria.fr/moose/view/Moose%205.0/?
> >
> > There still are a couple of issues with loading, but the builds do not look that bad.
> >
> > Cheers,
> > Doru
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
>
> --
> Andre Hora
>
>
>
> --
> Andre Hora
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: jenkins jobs on pharo 3.0

abergel
Thanks, I was able to use the standard debugger.

I had a look at DSM. The tests rely on the presence of a number of packages. For example, DSMCellTest>>setUp contains the following lines:

        importer model: MooseModel new; addFromPackagesNamed: #(#'Moose-TestResources-Dsm-PackageA' #'Moose-TestResources-Dsm-PackageB' #'Moose-TestResources-Dsm-PackageC' #'Moose-TestResources-Dsm-PackageD' #'Moose-TestResources-Dsm-PackageE' #'Moose-TestResources-Dsm-PackageF' #'Moose-TestResources-Dsm-PackageXExt'); run.

However, due to the new package organization of Pharo 3.0, there is only one package: 'Moose-TestResources-Dsm'. An easy way to fix the test is to update the test to deal with class categories right? I've tried, but maybe class extensions are not taken into account since the tests are yellow. Any idea what to do?

Pressing Cmd-L asks a stupid question now... This is frustrating... But well, nothing to do with Moose.

Cheers,
Alexandre



On Nov 2, 2013, at 8:26 AM, Tudor Girba <[hidden email]> wrote:

> It is due to the GTInspector being incompatible with the Pharo debugger.
>
> I opened the thread on the Pharo mailing list, and in the meantime we should not install the GTInspector. I cannot commit right now due to STHub being down, but you can fix it by reinstalling the default Spec-based inspector:
>
> EyeInspector registerToolsOn: Smalltalk tools.
>
> Cheers,
> Doru
>
>
>
>
> On Sat, Nov 2, 2013 at 12:17 PM, Alexandre Bergel <[hidden email]> wrote:
> Hi!
>
> I am having a look at build #28 of Moose 5.0.
> There is apparently heavily broken. Debuggers cannot be open anymore. Doiting "self halt" in a workspace opens the emergency evaluator.
>
> Hard to check what's going on with the failing tests.
> Am I the only one to see this?
>
> Cheers,
> Alexandre
>
>
> On Nov 2, 2013, at 4:47 AM, Tudor Girba <[hidden email]> wrote:
>
> > Thank you, Andre!
> >
> > Doru
> >
> >
> > On Sat, Nov 2, 2013 at 2:23 AM, Andre Hora <[hidden email]> wrote:
> > Brought it down to 15 tests failing.
> >
> > (The last build is red now because SH is down :|)
> >
> >
> > On Sat, Nov 2, 2013 at 12:58 AM, Andre Hora <[hidden email]> wrote:
> > Just fixed the 6 failing tests from gtoolkit related to the call to #versionImportPragmasVerifiedDefinedIn:
> > It is green now (but maybe a check should be done).
> >
> >
> >
> > On Sat, Nov 2, 2013 at 12:00 AM, Tudor Girba <[hidden email]> wrote:
> > Ok, I brought it down to: 33 tests failing in Moose (of which 3 are Glamour).
> >
> > The most important problem was induced by the (good) changes in the API of the RB visitor (visit methods are correctly called visit* instead of accept*).
> >
> > Cheers,
> > Doru
> >
> >
> >
> >
> > On Fri, Nov 1, 2013 at 7:07 PM, Tudor Girba <[hidden email]> wrote:
> > After about half an hour of work, all jobs build.
> >
> > Moose still has some 400 tests failing and Glamour a couple, but we are now in position to deal with them.
> >
> > Please feel free to take a look, and use the mailing list for coordination when you start looking into something more closely.
> >
> > Cheers,
> > Doru
> >
> >
> > On Fri, Nov 1, 2013 at 3:49 PM, Alexandre Bergel <[hidden email]> wrote:
> > Thanks Doru for this effort!
> >
> > Alexandre
> >
> >
> > On Nov 1, 2013, at 11:28 AM, Tudor Girba <[hidden email]> wrote:
> >
> > > Hi,
> > >
> > > I reconfigured all official Moose Jenkins jobs to work with Pharo 3.0:
> > > https://ci.inria.fr/moose/view/Moose%205.0/?
> > >
> > > There still are a couple of issues with loading, but the builds do not look that bad.
> > >
> > > Cheers,
> > > Doru
> > >
> > > --
> > > www.tudorgirba.com
> > >
> > > "Every thing has its own flow"
> > > _______________________________________________
> > > Moose-dev mailing list
> > > [hidden email]
> > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel  http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> >
> >
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> >
> >
> > --
> > Andre Hora
> >
> >
> >
> > --
> > Andre Hora
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> >
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: jenkins jobs on pharo 3.0

Tudor Girba-2
In reply to this post by Tudor Girba-2
I removed the GTInspector until the issue is fixed in Pharo.

Doru


On Sat, Nov 2, 2013 at 12:26 PM, Tudor Girba <[hidden email]> wrote:
It is due to the GTInspector being incompatible with the Pharo debugger.

I opened the thread on the Pharo mailing list, and in the meantime we should not install the GTInspector. I cannot commit right now due to STHub being down, but you can fix it by reinstalling the default Spec-based inspector:

EyeInspector registerToolsOn: Smalltalk tools.

Cheers,
Doru




On Sat, Nov 2, 2013 at 12:17 PM, Alexandre Bergel <[hidden email]> wrote:
Hi!

I am having a look at build #28 of Moose 5.0.
There is apparently heavily broken. Debuggers cannot be open anymore. Doiting "self halt" in a workspace opens the emergency evaluator.

Hard to check what's going on with the failing tests.
Am I the only one to see this?

Cheers,
Alexandre


On Nov 2, 2013, at 4:47 AM, Tudor Girba <[hidden email]> wrote:

> Thank you, Andre!
>
> Doru
>
>
> On Sat, Nov 2, 2013 at 2:23 AM, Andre Hora <[hidden email]> wrote:
> Brought it down to 15 tests failing.
>
> (The last build is red now because SH is down :|)
>
>
> On Sat, Nov 2, 2013 at 12:58 AM, Andre Hora <[hidden email]> wrote:
> Just fixed the 6 failing tests from gtoolkit related to the call to #versionImportPragmasVerifiedDefinedIn:
> It is green now (but maybe a check should be done).
>
>
>
> On Sat, Nov 2, 2013 at 12:00 AM, Tudor Girba <[hidden email]> wrote:
> Ok, I brought it down to: 33 tests failing in Moose (of which 3 are Glamour).
>
> The most important problem was induced by the (good) changes in the API of the RB visitor (visit methods are correctly called visit* instead of accept*).
>
> Cheers,
> Doru
>
>
>
>
> On Fri, Nov 1, 2013 at 7:07 PM, Tudor Girba <[hidden email]> wrote:
> After about half an hour of work, all jobs build.
>
> Moose still has some 400 tests failing and Glamour a couple, but we are now in position to deal with them.
>
> Please feel free to take a look, and use the mailing list for coordination when you start looking into something more closely.
>
> Cheers,
> Doru
>
>
> On Fri, Nov 1, 2013 at 3:49 PM, Alexandre Bergel <[hidden email]> wrote:
> Thanks Doru for this effort!
>
> Alexandre
>
>
> On Nov 1, 2013, at 11:28 AM, Tudor Girba <[hidden email]> wrote:
>
> > Hi,
> >
> > I reconfigured all official Moose Jenkins jobs to work with Pharo 3.0:
> > https://ci.inria.fr/moose/view/Moose%205.0/?
> >
> > There still are a couple of issues with loading, but the builds do not look that bad.
> >
> > Cheers,
> > Doru
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
>
> --
> Andre Hora
>
>
>
> --
> Andre Hora
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: jenkins jobs on pharo 3.0

Tudor Girba-2
In reply to this post by abergel
The DSM tests have to be moved to rely on RPackage. We should remove the category importer because we do not need to support this use case, now that categories are no longer central in Pharo.

Doru


On Sat, Nov 2, 2013 at 5:04 PM, Alexandre Bergel <[hidden email]> wrote:
Thanks, I was able to use the standard debugger.

I had a look at DSM. The tests rely on the presence of a number of packages. For example, DSMCellTest>>setUp contains the following lines:

        importer model: MooseModel new; addFromPackagesNamed: #(#'Moose-TestResources-Dsm-PackageA' #'Moose-TestResources-Dsm-PackageB' #'Moose-TestResources-Dsm-PackageC' #'Moose-TestResources-Dsm-PackageD' #'Moose-TestResources-Dsm-PackageE' #'Moose-TestResources-Dsm-PackageF' #'Moose-TestResources-Dsm-PackageXExt'); run.

However, due to the new package organization of Pharo 3.0, there is only one package: 'Moose-TestResources-Dsm'. An easy way to fix the test is to update the test to deal with class categories right? I've tried, but maybe class extensions are not taken into account since the tests are yellow. Any idea what to do?

Pressing Cmd-L asks a stupid question now... This is frustrating... But well, nothing to do with Moose.

Cheers,
Alexandre



On Nov 2, 2013, at 8:26 AM, Tudor Girba <[hidden email]> wrote:

> It is due to the GTInspector being incompatible with the Pharo debugger.
>
> I opened the thread on the Pharo mailing list, and in the meantime we should not install the GTInspector. I cannot commit right now due to STHub being down, but you can fix it by reinstalling the default Spec-based inspector:
>
> EyeInspector registerToolsOn: Smalltalk tools.
>
> Cheers,
> Doru
>
>
>
>
> On Sat, Nov 2, 2013 at 12:17 PM, Alexandre Bergel <[hidden email]> wrote:
> Hi!
>
> I am having a look at build #28 of Moose 5.0.
> There is apparently heavily broken. Debuggers cannot be open anymore. Doiting "self halt" in a workspace opens the emergency evaluator.
>
> Hard to check what's going on with the failing tests.
> Am I the only one to see this?
>
> Cheers,
> Alexandre
>
>
> On Nov 2, 2013, at 4:47 AM, Tudor Girba <[hidden email]> wrote:
>
> > Thank you, Andre!
> >
> > Doru
> >
> >
> > On Sat, Nov 2, 2013 at 2:23 AM, Andre Hora <[hidden email]> wrote:
> > Brought it down to 15 tests failing.
> >
> > (The last build is red now because SH is down :|)
> >
> >
> > On Sat, Nov 2, 2013 at 12:58 AM, Andre Hora <[hidden email]> wrote:
> > Just fixed the 6 failing tests from gtoolkit related to the call to #versionImportPragmasVerifiedDefinedIn:
> > It is green now (but maybe a check should be done).
> >
> >
> >
> > On Sat, Nov 2, 2013 at 12:00 AM, Tudor Girba <[hidden email]> wrote:
> > Ok, I brought it down to: 33 tests failing in Moose (of which 3 are Glamour).
> >
> > The most important problem was induced by the (good) changes in the API of the RB visitor (visit methods are correctly called visit* instead of accept*).
> >
> > Cheers,
> > Doru
> >
> >
> >
> >
> > On Fri, Nov 1, 2013 at 7:07 PM, Tudor Girba <[hidden email]> wrote:
> > After about half an hour of work, all jobs build.
> >
> > Moose still has some 400 tests failing and Glamour a couple, but we are now in position to deal with them.
> >
> > Please feel free to take a look, and use the mailing list for coordination when you start looking into something more closely.
> >
> > Cheers,
> > Doru
> >
> >
> > On Fri, Nov 1, 2013 at 3:49 PM, Alexandre Bergel <[hidden email]> wrote:
> > Thanks Doru for this effort!
> >
> > Alexandre
> >
> >
> > On Nov 1, 2013, at 11:28 AM, Tudor Girba <[hidden email]> wrote:
> >
> > > Hi,
> > >
> > > I reconfigured all official Moose Jenkins jobs to work with Pharo 3.0:
> > > https://ci.inria.fr/moose/view/Moose%205.0/?
> > >
> > > There still are a couple of issues with loading, but the builds do not look that bad.
> > >
> > > Cheers,
> > > Doru
> > >
> > > --
> > > www.tudorgirba.com
> > >
> > > "Every thing has its own flow"
> > > _______________________________________________
> > > Moose-dev mailing list
> > > [hidden email]
> > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel  http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> >
> >
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> >
> >
> > --
> > Andre Hora
> >
> >
> >
> > --
> > Andre Hora
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> >
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: jenkins jobs on pharo 3.0

Tudor Girba-2
We have 10 failures left:
- 3 from Glamour that are due to one Announcement-related issue. Andrei is looking into this.
- 7 from DSM that seem to be due to the CategoryImporter, and that should be moved to the PackageImporter. Anyone wants to look into this?

Doru


On Sat, Nov 2, 2013 at 11:30 PM, Tudor Girba <[hidden email]> wrote:
The DSM tests have to be moved to rely on RPackage. We should remove the category importer because we do not need to support this use case, now that categories are no longer central in Pharo.

Doru


On Sat, Nov 2, 2013 at 5:04 PM, Alexandre Bergel <[hidden email]> wrote:
Thanks, I was able to use the standard debugger.

I had a look at DSM. The tests rely on the presence of a number of packages. For example, DSMCellTest>>setUp contains the following lines:

        importer model: MooseModel new; addFromPackagesNamed: #(#'Moose-TestResources-Dsm-PackageA' #'Moose-TestResources-Dsm-PackageB' #'Moose-TestResources-Dsm-PackageC' #'Moose-TestResources-Dsm-PackageD' #'Moose-TestResources-Dsm-PackageE' #'Moose-TestResources-Dsm-PackageF' #'Moose-TestResources-Dsm-PackageXExt'); run.

However, due to the new package organization of Pharo 3.0, there is only one package: 'Moose-TestResources-Dsm'. An easy way to fix the test is to update the test to deal with class categories right? I've tried, but maybe class extensions are not taken into account since the tests are yellow. Any idea what to do?

Pressing Cmd-L asks a stupid question now... This is frustrating... But well, nothing to do with Moose.

Cheers,
Alexandre



On Nov 2, 2013, at 8:26 AM, Tudor Girba <[hidden email]> wrote:

> It is due to the GTInspector being incompatible with the Pharo debugger.
>
> I opened the thread on the Pharo mailing list, and in the meantime we should not install the GTInspector. I cannot commit right now due to STHub being down, but you can fix it by reinstalling the default Spec-based inspector:
>
> EyeInspector registerToolsOn: Smalltalk tools.
>
> Cheers,
> Doru
>
>
>
>
> On Sat, Nov 2, 2013 at 12:17 PM, Alexandre Bergel <[hidden email]> wrote:
> Hi!
>
> I am having a look at build #28 of Moose 5.0.
> There is apparently heavily broken. Debuggers cannot be open anymore. Doiting "self halt" in a workspace opens the emergency evaluator.
>
> Hard to check what's going on with the failing tests.
> Am I the only one to see this?
>
> Cheers,
> Alexandre
>
>
> On Nov 2, 2013, at 4:47 AM, Tudor Girba <[hidden email]> wrote:
>
> > Thank you, Andre!
> >
> > Doru
> >
> >
> > On Sat, Nov 2, 2013 at 2:23 AM, Andre Hora <[hidden email]> wrote:
> > Brought it down to 15 tests failing.
> >
> > (The last build is red now because SH is down :|)
> >
> >
> > On Sat, Nov 2, 2013 at 12:58 AM, Andre Hora <[hidden email]> wrote:
> > Just fixed the 6 failing tests from gtoolkit related to the call to #versionImportPragmasVerifiedDefinedIn:
> > It is green now (but maybe a check should be done).
> >
> >
> >
> > On Sat, Nov 2, 2013 at 12:00 AM, Tudor Girba <[hidden email]> wrote:
> > Ok, I brought it down to: 33 tests failing in Moose (of which 3 are Glamour).
> >
> > The most important problem was induced by the (good) changes in the API of the RB visitor (visit methods are correctly called visit* instead of accept*).
> >
> > Cheers,
> > Doru
> >
> >
> >
> >
> > On Fri, Nov 1, 2013 at 7:07 PM, Tudor Girba <[hidden email]> wrote:
> > After about half an hour of work, all jobs build.
> >
> > Moose still has some 400 tests failing and Glamour a couple, but we are now in position to deal with them.
> >
> > Please feel free to take a look, and use the mailing list for coordination when you start looking into something more closely.
> >
> > Cheers,
> > Doru
> >
> >
> > On Fri, Nov 1, 2013 at 3:49 PM, Alexandre Bergel <[hidden email]> wrote:
> > Thanks Doru for this effort!
> >
> > Alexandre
> >
> >
> > On Nov 1, 2013, at 11:28 AM, Tudor Girba <[hidden email]> wrote:
> >
> > > Hi,
> > >
> > > I reconfigured all official Moose Jenkins jobs to work with Pharo 3.0:
> > > https://ci.inria.fr/moose/view/Moose%205.0/?
> > >
> > > There still are a couple of issues with loading, but the builds do not look that bad.
> > >
> > > Cheers,
> > > Doru
> > >
> > > --
> > > www.tudorgirba.com
> > >
> > > "Every thing has its own flow"
> > > _______________________________________________
> > > Moose-dev mailing list
> > > [hidden email]
> > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel  http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> >
> >
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> >
> >
> > --
> > Andre Hora
> >
> >
> >
> > --
> > Andre Hora
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> >
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: jenkins jobs on pharo 3.0

Andrei Chis
The Glamour build is green again :)

Cheers,
Andrei


On Sun, Nov 3, 2013 at 10:08 AM, Tudor Girba <[hidden email]> wrote:
We have 10 failures left:
- 3 from Glamour that are due to one Announcement-related issue. Andrei is looking into this.
- 7 from DSM that seem to be due to the CategoryImporter, and that should be moved to the PackageImporter. Anyone wants to look into this?

Doru


On Sat, Nov 2, 2013 at 11:30 PM, Tudor Girba <[hidden email]> wrote:
The DSM tests have to be moved to rely on RPackage. We should remove the category importer because we do not need to support this use case, now that categories are no longer central in Pharo.

Doru


On Sat, Nov 2, 2013 at 5:04 PM, Alexandre Bergel <[hidden email]> wrote:
Thanks, I was able to use the standard debugger.

I had a look at DSM. The tests rely on the presence of a number of packages. For example, DSMCellTest>>setUp contains the following lines:

        importer model: MooseModel new; addFromPackagesNamed: #(#'Moose-TestResources-Dsm-PackageA' #'Moose-TestResources-Dsm-PackageB' #'Moose-TestResources-Dsm-PackageC' #'Moose-TestResources-Dsm-PackageD' #'Moose-TestResources-Dsm-PackageE' #'Moose-TestResources-Dsm-PackageF' #'Moose-TestResources-Dsm-PackageXExt'); run.

However, due to the new package organization of Pharo 3.0, there is only one package: 'Moose-TestResources-Dsm'. An easy way to fix the test is to update the test to deal with class categories right? I've tried, but maybe class extensions are not taken into account since the tests are yellow. Any idea what to do?

Pressing Cmd-L asks a stupid question now... This is frustrating... But well, nothing to do with Moose.

Cheers,
Alexandre



On Nov 2, 2013, at 8:26 AM, Tudor Girba <[hidden email]> wrote:

> It is due to the GTInspector being incompatible with the Pharo debugger.
>
> I opened the thread on the Pharo mailing list, and in the meantime we should not install the GTInspector. I cannot commit right now due to STHub being down, but you can fix it by reinstalling the default Spec-based inspector:
>
> EyeInspector registerToolsOn: Smalltalk tools.
>
> Cheers,
> Doru
>
>
>
>
> On Sat, Nov 2, 2013 at 12:17 PM, Alexandre Bergel <[hidden email]> wrote:
> Hi!
>
> I am having a look at build #28 of Moose 5.0.
> There is apparently heavily broken. Debuggers cannot be open anymore. Doiting "self halt" in a workspace opens the emergency evaluator.
>
> Hard to check what's going on with the failing tests.
> Am I the only one to see this?
>
> Cheers,
> Alexandre
>
>
> On Nov 2, 2013, at 4:47 AM, Tudor Girba <[hidden email]> wrote:
>
> > Thank you, Andre!
> >
> > Doru
> >
> >
> > On Sat, Nov 2, 2013 at 2:23 AM, Andre Hora <[hidden email]> wrote:
> > Brought it down to 15 tests failing.
> >
> > (The last build is red now because SH is down :|)
> >
> >
> > On Sat, Nov 2, 2013 at 12:58 AM, Andre Hora <[hidden email]> wrote:
> > Just fixed the 6 failing tests from gtoolkit related to the call to #versionImportPragmasVerifiedDefinedIn:
> > It is green now (but maybe a check should be done).
> >
> >
> >
> > On Sat, Nov 2, 2013 at 12:00 AM, Tudor Girba <[hidden email]> wrote:
> > Ok, I brought it down to: 33 tests failing in Moose (of which 3 are Glamour).
> >
> > The most important problem was induced by the (good) changes in the API of the RB visitor (visit methods are correctly called visit* instead of accept*).
> >
> > Cheers,
> > Doru
> >
> >
> >
> >
> > On Fri, Nov 1, 2013 at 7:07 PM, Tudor Girba <[hidden email]> wrote:
> > After about half an hour of work, all jobs build.
> >
> > Moose still has some 400 tests failing and Glamour a couple, but we are now in position to deal with them.
> >
> > Please feel free to take a look, and use the mailing list for coordination when you start looking into something more closely.
> >
> > Cheers,
> > Doru
> >
> >
> > On Fri, Nov 1, 2013 at 3:49 PM, Alexandre Bergel <[hidden email]> wrote:
> > Thanks Doru for this effort!
> >
> > Alexandre
> >
> >
> > On Nov 1, 2013, at 11:28 AM, Tudor Girba <[hidden email]> wrote:
> >
> > > Hi,
> > >
> > > I reconfigured all official Moose Jenkins jobs to work with Pharo 3.0:
> > > https://ci.inria.fr/moose/view/Moose%205.0/?
> > >
> > > There still are a couple of issues with loading, but the builds do not look that bad.
> > >
> > > Cheers,
> > > Doru
> > >
> > > --
> > > www.tudorgirba.com
> > >
> > > "Every thing has its own flow"
> > > _______________________________________________
> > > Moose-dev mailing list
> > > [hidden email]
> > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel  http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> >
> >
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> >
> >
> > --
> > Andre Hora
> >
> >
> >
> > --
> > Andre Hora
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> >
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: jenkins jobs on pharo 3.0

Tudor Girba-2
Great!

Doru


On Sun, Nov 3, 2013 at 12:50 PM, Andrei Chis <[hidden email]> wrote:
The Glamour build is green again :)

Cheers,
Andrei


On Sun, Nov 3, 2013 at 10:08 AM, Tudor Girba <[hidden email]> wrote:
We have 10 failures left:
- 3 from Glamour that are due to one Announcement-related issue. Andrei is looking into this.
- 7 from DSM that seem to be due to the CategoryImporter, and that should be moved to the PackageImporter. Anyone wants to look into this?

Doru


On Sat, Nov 2, 2013 at 11:30 PM, Tudor Girba <[hidden email]> wrote:
The DSM tests have to be moved to rely on RPackage. We should remove the category importer because we do not need to support this use case, now that categories are no longer central in Pharo.

Doru


On Sat, Nov 2, 2013 at 5:04 PM, Alexandre Bergel <[hidden email]> wrote:
Thanks, I was able to use the standard debugger.

I had a look at DSM. The tests rely on the presence of a number of packages. For example, DSMCellTest>>setUp contains the following lines:

        importer model: MooseModel new; addFromPackagesNamed: #(#'Moose-TestResources-Dsm-PackageA' #'Moose-TestResources-Dsm-PackageB' #'Moose-TestResources-Dsm-PackageC' #'Moose-TestResources-Dsm-PackageD' #'Moose-TestResources-Dsm-PackageE' #'Moose-TestResources-Dsm-PackageF' #'Moose-TestResources-Dsm-PackageXExt'); run.

However, due to the new package organization of Pharo 3.0, there is only one package: 'Moose-TestResources-Dsm'. An easy way to fix the test is to update the test to deal with class categories right? I've tried, but maybe class extensions are not taken into account since the tests are yellow. Any idea what to do?

Pressing Cmd-L asks a stupid question now... This is frustrating... But well, nothing to do with Moose.

Cheers,
Alexandre



On Nov 2, 2013, at 8:26 AM, Tudor Girba <[hidden email]> wrote:

> It is due to the GTInspector being incompatible with the Pharo debugger.
>
> I opened the thread on the Pharo mailing list, and in the meantime we should not install the GTInspector. I cannot commit right now due to STHub being down, but you can fix it by reinstalling the default Spec-based inspector:
>
> EyeInspector registerToolsOn: Smalltalk tools.
>
> Cheers,
> Doru
>
>
>
>
> On Sat, Nov 2, 2013 at 12:17 PM, Alexandre Bergel <[hidden email]> wrote:
> Hi!
>
> I am having a look at build #28 of Moose 5.0.
> There is apparently heavily broken. Debuggers cannot be open anymore. Doiting "self halt" in a workspace opens the emergency evaluator.
>
> Hard to check what's going on with the failing tests.
> Am I the only one to see this?
>
> Cheers,
> Alexandre
>
>
> On Nov 2, 2013, at 4:47 AM, Tudor Girba <[hidden email]> wrote:
>
> > Thank you, Andre!
> >
> > Doru
> >
> >
> > On Sat, Nov 2, 2013 at 2:23 AM, Andre Hora <[hidden email]> wrote:
> > Brought it down to 15 tests failing.
> >
> > (The last build is red now because SH is down :|)
> >
> >
> > On Sat, Nov 2, 2013 at 12:58 AM, Andre Hora <[hidden email]> wrote:
> > Just fixed the 6 failing tests from gtoolkit related to the call to #versionImportPragmasVerifiedDefinedIn:
> > It is green now (but maybe a check should be done).
> >
> >
> >
> > On Sat, Nov 2, 2013 at 12:00 AM, Tudor Girba <[hidden email]> wrote:
> > Ok, I brought it down to: 33 tests failing in Moose (of which 3 are Glamour).
> >
> > The most important problem was induced by the (good) changes in the API of the RB visitor (visit methods are correctly called visit* instead of accept*).
> >
> > Cheers,
> > Doru
> >
> >
> >
> >
> > On Fri, Nov 1, 2013 at 7:07 PM, Tudor Girba <[hidden email]> wrote:
> > After about half an hour of work, all jobs build.
> >
> > Moose still has some 400 tests failing and Glamour a couple, but we are now in position to deal with them.
> >
> > Please feel free to take a look, and use the mailing list for coordination when you start looking into something more closely.
> >
> > Cheers,
> > Doru
> >
> >
> > On Fri, Nov 1, 2013 at 3:49 PM, Alexandre Bergel <[hidden email]> wrote:
> > Thanks Doru for this effort!
> >
> > Alexandre
> >
> >
> > On Nov 1, 2013, at 11:28 AM, Tudor Girba <[hidden email]> wrote:
> >
> > > Hi,
> > >
> > > I reconfigured all official Moose Jenkins jobs to work with Pharo 3.0:
> > > https://ci.inria.fr/moose/view/Moose%205.0/?
> > >
> > > There still are a couple of issues with loading, but the builds do not look that bad.
> > >
> > > Cheers,
> > > Doru
> > >
> > > --
> > > www.tudorgirba.com
> > >
> > > "Every thing has its own flow"
> > > _______________________________________________
> > > Moose-dev mailing list
> > > [hidden email]
> > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel  http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> >
> >
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> >
> >
> > --
> > Andre Hora
> >
> >
> >
> > --
> > Andre Hora
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> >
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev




--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: jenkins jobs on pharo 3.0

abergel
> - 7 from DSM that seem to be due to the CategoryImporter, and that should be moved to the PackageImporter. Anyone wants to look into this?

I am working on these right now...

Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev