Jenkins build became unstable: moose-latest-dev-4.8 #200

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

Jenkins build became unstable: moose-latest-dev-4.8 #200

admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/200/>

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

Jenkins build is still unstable: moose-latest-dev-4.8 #201

admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/201/>

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

Jenkins build is still unstable: moose-latest-dev-4.8 #202

admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/202/>

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

Jenkins build is still unstable: moose-latest-dev-4.8 #203

admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/203/>

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

Jenkins build is still unstable: moose-latest-dev-4.8 #204

admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/204/>

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

Jenkins build is still unstable: moose-latest-dev-4.8 #205

admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/205/>

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

Jenkins build is still unstable: moose-latest-dev-4.8 #206

admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/206/>

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

Jenkins build is still unstable: moose-latest-dev-4.8 #207

admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/207/>

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

Jenkins build is still unstable: moose-latest-dev-4.8 #208

admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/208/>

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

Jenkins build is still unstable: moose-latest-dev-4.8 #209

admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/209/>

_______________________________________________
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 build is still unstable: moose-latest-dev-4.8 #209

Tudor Girba-2
There are two tests that fail related to SmalltalkImporter/FAMIX and SmallDude

        • Moose.Tests.SmalltalkImporter.Core.FamixPropertiesTest.testHasTheSamePropertiesAs
        • SmallDude.Tests.Core.DudeMooseSmalltalkTest.testMSEImportExport

Does anyone want to investigate?

Cheers,
Doru


On Apr 5, 2013, at 3:24 AM, [hidden email] wrote:

> See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/209/>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"If you interrupt the barber while he is cutting your hair,
you will end up with a messy haircut."


_______________________________________________
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 build is still unstable: moose-latest-dev-4.8 #209

abergel
I think I will have some time today

Alexandre

On 5 Apr 2013, at 01:41, Tudor Girba <[hidden email]> wrote:

> There are two tests that fail related to SmalltalkImporter/FAMIX and SmallDude
>
>    • Moose.Tests.SmalltalkImporter.Core.FamixPropertiesTest.testHasTheSamePropertiesAs
>    • SmallDude.Tests.Core.DudeMooseSmalltalkTest.testMSEImportExport
>
> Does anyone want to investigate?
>
> Cheers,
> Doru
>
>
> On Apr 5, 2013, at 3:24 AM, [hidden email] wrote:
>
>> See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/209/>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "If you interrupt the barber while he is cutting your hair,
> you will end up with a messy haircut."
>
>
> _______________________________________________
> 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 build is still unstable: moose-latest-dev-4.8 #209

abergel
In reply to this post by Tudor Girba-2
Hi!

I had a look at the failing tests.

> • Moose.Tests.SmalltalkImporter.Core.FamixPropertiesTest.testHasTheSamePropertiesAs

I've tried:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| c model |
model := MooseModel new.
c := FAMIXClass new.
c name: 'C'.

model add: c.
c hasTheSamePropertiesAs: c. " => false " "Should be true I guess"

c allDeclaredProperties detect:  [ :each | (each getFrom: c) ~= (each getFrom: c) ] ifNone: [  'Everything is okay!' ]
"=>  a FM3PropertyDescription[FAMIX.Type.Provider classes]"
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

This FAMIX.Type.Provider classes comes from the following methods:

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
FAMIXType>>providerClasses
        "returns a set of all the classes that the receiver depends on (inherites, staticly accesses, or uses some of their methods)"
        <MSEProperty: 'Provider classes' type: #FAMIXType> <multivalued>

        ^ self queryAllOutgoingAssociations atClassScope withoutSelfLoops


FAMIXMethod>>providerClasses
        "returns a set of all the classes that the receiver depends on (inherites, staticly accesses, or uses some of their methods)"
        <MSEProperty: 'Provider classes' type: #FAMIXType> <multivalued>

        ^ self queryAllOutgoingAssociations atClassScope withoutSelfLoops
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

I guess the annotation should instead be: <MSEProperty: #providerClasses  type: #FAMIXType> <multivalued>

However the tests are fill yellow (I did not forget to reset the meta description).

Doru, Can you see what is wrong? Does this help?


> • SmallDude.Tests.Core.DudeMooseSmalltalkTest.testMSEImportExport

If we make #testHasTheSamePropertiesAs, then #testMSEImportExport will also be greener. The latter depends on the first.

Alexandre

>
>
>
> On Apr 5, 2013, at 3:24 AM, [hidden email] wrote:
>
>> See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/209/>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "If you interrupt the barber while he is cutting your hair,
> you will end up with a messy haircut."
>
>
> _______________________________________________
> 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
|

Jenkins build is still unstable: moose-latest-dev-4.8 #210

admin-2
In reply to this post by admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/210/>

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

Jenkins build is still unstable: moose-latest-dev-4.8 #211

admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/211/>

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

Jenkins build is still unstable: moose-latest-dev-4.8 #212

admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/212/>

_______________________________________________
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 build is still unstable: moose-latest-dev-4.8 #209

Tudor Girba-2
In reply to this post by abergel
Thanks Alex,

I could manage to isolate the issue. The problem was that MooseQueryResult did not have = defined, and thus, it did not behave like a collection. I added one now, and those tests are green.

However, now we have another failing test that was somehow induced by the newly added = method.
FAMIXExtensionMetricTest>>testBunchCouplingFAMIXPackage

@Nicolas, could you take a look. There is only one assertion that fails and I just cannot see how the newly added method makes the difference in the bunch computation (I checked: if you remove the method, the bunch test is green again).

Cheers,
Doru


On Apr 5, 2013, at 9:40 PM, Alexandre Bergel <[hidden email]> wrote:

> Hi!
>
> I had a look at the failing tests.
>
>> • Moose.Tests.SmalltalkImporter.Core.FamixPropertiesTest.testHasTheSamePropertiesAs
>
> I've tried:
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> | c model |
> model := MooseModel new.
> c := FAMIXClass new.
> c name: 'C'.
>
> model add: c.
> c hasTheSamePropertiesAs: c. " => false " "Should be true I guess"
>
> c allDeclaredProperties detect:  [ :each | (each getFrom: c) ~= (each getFrom: c) ] ifNone: [  'Everything is okay!' ]
> "=>  a FM3PropertyDescription[FAMIX.Type.Provider classes]"
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> This FAMIX.Type.Provider classes comes from the following methods:
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> FAMIXType>>providerClasses
> "returns a set of all the classes that the receiver depends on (inherites, staticly accesses, or uses some of their methods)"
> <MSEProperty: 'Provider classes' type: #FAMIXType> <multivalued>
>
> ^ self queryAllOutgoingAssociations atClassScope withoutSelfLoops
>
>
> FAMIXMethod>>providerClasses
> "returns a set of all the classes that the receiver depends on (inherites, staticly accesses, or uses some of their methods)"
> <MSEProperty: 'Provider classes' type: #FAMIXType> <multivalued>
>
> ^ self queryAllOutgoingAssociations atClassScope withoutSelfLoops
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> I guess the annotation should instead be: <MSEProperty: #providerClasses  type: #FAMIXType> <multivalued>
>
> However the tests are fill yellow (I did not forget to reset the meta description).
>
> Doru, Can you see what is wrong? Does this help?
>
>
>> • SmallDude.Tests.Core.DudeMooseSmalltalkTest.testMSEImportExport
>
> If we make #testHasTheSamePropertiesAs, then #testMSEImportExport will also be greener. The latter depends on the first.
>
> Alexandre
>>
>>
>>
>> On Apr 5, 2013, at 3:24 AM, [hidden email] wrote:
>>
>>> See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/209/>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> www.tudorgirba.com
>>
>> "If you interrupt the barber while he is cutting your hair,
>> you will end up with a messy haircut."
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>

--
www.tudorgirba.com

"Sometimes the best solution is not the best solution."


_______________________________________________
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 build is still unstable: moose-latest-dev-4.8 #209

abergel
Ok!

Alexandre


On Apr 5, 2013, at 4:27 PM, Tudor Girba <[hidden email]> wrote:

> Thanks Alex,
>
> I could manage to isolate the issue. The problem was that MooseQueryResult did not have = defined, and thus, it did not behave like a collection. I added one now, and those tests are green.
>
> However, now we have another failing test that was somehow induced by the newly added = method.
> FAMIXExtensionMetricTest>>testBunchCouplingFAMIXPackage
>
> @Nicolas, could you take a look. There is only one assertion that fails and I just cannot see how the newly added method makes the difference in the bunch computation (I checked: if you remove the method, the bunch test is green again).
>
> Cheers,
> Doru
>
>
> On Apr 5, 2013, at 9:40 PM, Alexandre Bergel <[hidden email]> wrote:
>
>> Hi!
>>
>> I had a look at the failing tests.
>>
>>> • Moose.Tests.SmalltalkImporter.Core.FamixPropertiesTest.testHasTheSamePropertiesAs
>>
>> I've tried:
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>> | c model |
>> model := MooseModel new.
>> c := FAMIXClass new.
>> c name: 'C'.
>>
>> model add: c.
>> c hasTheSamePropertiesAs: c. " => false " "Should be true I guess"
>>
>> c allDeclaredProperties detect:  [ :each | (each getFrom: c) ~= (each getFrom: c) ] ifNone: [  'Everything is okay!' ]
>> "=>  a FM3PropertyDescription[FAMIX.Type.Provider classes]"
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>>
>> This FAMIX.Type.Provider classes comes from the following methods:
>>
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>> FAMIXType>>providerClasses
>> "returns a set of all the classes that the receiver depends on (inherites, staticly accesses, or uses some of their methods)"
>> <MSEProperty: 'Provider classes' type: #FAMIXType> <multivalued>
>>
>> ^ self queryAllOutgoingAssociations atClassScope withoutSelfLoops
>>
>>
>> FAMIXMethod>>providerClasses
>> "returns a set of all the classes that the receiver depends on (inherites, staticly accesses, or uses some of their methods)"
>> <MSEProperty: 'Provider classes' type: #FAMIXType> <multivalued>
>>
>> ^ self queryAllOutgoingAssociations atClassScope withoutSelfLoops
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>>
>> I guess the annotation should instead be: <MSEProperty: #providerClasses  type: #FAMIXType> <multivalued>
>>
>> However the tests are fill yellow (I did not forget to reset the meta description).
>>
>> Doru, Can you see what is wrong? Does this help?
>>
>>
>>> • SmallDude.Tests.Core.DudeMooseSmalltalkTest.testMSEImportExport
>>
>> If we make #testHasTheSamePropertiesAs, then #testMSEImportExport will also be greener. The latter depends on the first.
>>
>> Alexandre
>>>
>>>
>>>
>>> On Apr 5, 2013, at 3:24 AM, [hidden email] wrote:
>>>
>>>> See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/209/>
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> [hidden email]
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "If you interrupt the barber while he is cutting your hair,
>>> you will end up with a messy haircut."
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>
> --
> www.tudorgirba.com
>
> "Sometimes the best solution is not the best solution."
>

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
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
|

Jenkins build is still unstable: moose-latest-dev-4.8 #213

admin-2
In reply to this post by admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/213/>

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

Jenkins build is still unstable: moose-latest-dev-4.8 #214

admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/214/>

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