4 Apr
4 Apr
2:46 a.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #201
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/201/>
3:24 a.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #202
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/202/>
3:57 a.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #203
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/203/>
4:37 a.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #204
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/204/>
2:21 p.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #205
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/205/>
2:54 p.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #206
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/206/>
3:33 p.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #207
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/207/>
5 Apr
5 Apr
2:46 a.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #208
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/208/>
3:24 a.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #209
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/209/>
7:41 a.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #209
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, admin(a)moosetechnology.org wrote:
See
<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/209/>
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
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."
2:19 p.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #209
I think I will have some time today
Alexandre
On 5 Apr 2013, at 01:41, Tudor Girba <tudor(a)tudorgirba.com> 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, admin(a)moosetechnology.org wrote:
See
<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/209/>
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
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
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
9:40 p.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #209
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, admin(a)moosetechnology.org wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
See
<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/209/>
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
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
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
10:27 p.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #209
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 <alexandre.bergel(a)me.com> wrote:
Hi!
I had a look at the failing tests.
--
www.tudorgirba.com
"Sometimes the best solution is not the best solution."
•
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, admin(a)moosetechnology.org wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
See
<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/209/>
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
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
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
11:29 p.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #209
Ok!
Alexandre
On Apr 5, 2013, at 4:27 PM, Tudor Girba <tudor(a)tudorgirba.com> 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 <alexandre.bergel(a)me.com> wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
I had a look at the failing tests.
--
www.tudorgirba.com
"Sometimes the best solution is not the best solution."
•
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, admin(a)moosetechnology.org wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
See
<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/209/>
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
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
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
21 Apr
21 Apr
9:35 p.m.
New subject: testBunchCouplingFAMIXPackage [was: Re: Jenkins build is still unstable: moose-latest-dev-4.8 #209]
Hi Nicolas,
The following test fails right now:
FAMIXExtensionMetricTest>>testBunchCouplingFAMIXPackage
The failure was introduced when I added MooseQueryResult>>= (see details below).
However, I do not understand why this newly added method would have an influence.
The funny thing is that only one assertion is problematic:
self assert: (p3m2 bunchCouplingWith: p1m2) = (4/54) asFloat.
All the other assertion are valid. I looked at the code but could not see anything (also
because the computation is rather complex). Could you check please?
Cheers,
Doru
On Apr 5, 2013, at 10:27 PM, Tudor Girba <tudor(a)tudorgirba.com> 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 <alexandre.bergel(a)me.com> wrote:
--
www.tudorgirba.com
"Reasonable is what we are accustomed with."
Hi!
I had a look at the failing tests.
--
www.tudorgirba.com
"Sometimes the best solution is not the best solution."
•
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, admin(a)moosetechnology.org wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
See
<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/209/>
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
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
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
5 Apr
5 Apr
10:50 p.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #210
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/210/>
11:24 p.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #211
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/211/>
11:55 p.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #212
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/212/>
6 Apr
6 Apr
12:47 a.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #213
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/213/>
1:19 a.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #214
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/214/>
2:47 a.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #215
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/215/>
3:25 a.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #216
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/216/>
11:51 p.m.
New subject: Jenkins build is still unstable: moose-latest-dev-4.8 #217
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/217/>
7 Apr
7 Apr
2:46 a.m.
New subject: Build failed in Jenkins: moose-latest-dev-4.8 #218
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/218/>
------------------------------------------
Started by timer
Building remotely on moose-slave in workspace
<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/>
Deleting project workspace... done
[moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson5874479847361215715.sh
+ bash
+ wget --quiet -O - http://get.pharo.org/20+vmLatest
Downloading the latest 20 Image:
http://files.pharo.org/image/20/latest.zip
image.TBv9R/Pharo-20596.image
Downloading the latest pharoVM:
http://files.pharo.org/vm/pharo/linux/pharo-linux-latest.zip
pharo-vm/pharo
Downloading PharoV10.sources:
http://files.pharo.org/image//PharoV10.sources.zip
Downloading PharoV20.sources:
http://files.pharo.org/image//PharoV20.sources.zip
Creating starter scripts pharo and pharo-ui
Please install the 32bit libraries
sudo aptitude install ia32-libs
+ ./vm.sh Pharo.image save moose-latest-dev-4.8
+ REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main
+ ./vm.sh moose-latest-dev-4.8.image config
http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose
--install=development
[31m[33m
===============================================================================
Notice: Installing ConfigurationOfMoose development
===============================================================================
[0m[0m+ ./vm.sh moose-latest-dev-4.8.image mooseimagesetup
+ ./vm.sh moose-latest-dev-4.8.image moosetest --junit-xml-output
[31m[33m
===============================================================================
Notice: Running tests in 126 Packages
===============================================================================
[0m[0m+ mv ./vm/PharoV20.sources ./
mv: cannot stat `./vm/PharoV20.sources': No such file or directory
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
4:22 p.m.
New subject: Build failed in Jenkins: moose-latest-dev-4.8 #219
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/219/>
------------------------------------------
[URLTrigger] A change within the response URL invocation (log)
Building remotely on moose-slave in workspace
<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/>
Deleting project workspace... done
[moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson5689926344806956705.sh
+ bash
+ wget --quiet -O - http://get.pharo.org/20+vmLatest
Downloading the latest 20 Image:
http://files.pharo.org/image/20/latest.zip
image.TW2BI/Pharo-20596.image
Downloading the latest pharoVM:
http://files.pharo.org/vm/pharo/linux/pharo-linux-latest.zip
pharo-vm/pharo
Downloading PharoV10.sources:
http://files.pharo.org/image//PharoV10.sources.zip
Downloading PharoV20.sources:
http://files.pharo.org/image//PharoV20.sources.zip
Creating starter scripts pharo and pharo-ui
Please install the 32bit libraries
sudo aptitude install ia32-libs
+ ./vm.sh Pharo.image save moose-latest-dev-4.8
+ REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main
+ ./vm.sh moose-latest-dev-4.8.image config
http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose
--install=development
[31m[33m
===============================================================================
Notice: Installing ConfigurationOfMoose development
===============================================================================
[0m[0m+ ./vm.sh moose-latest-dev-4.8.image mooseimagesetup
+ ./vm.sh moose-latest-dev-4.8.image moosetest --junit-xml-output
[31m[33m
===============================================================================
Notice: Running tests in 126 Packages
===============================================================================
[0m[0m+ mv ./vm/PharoV20.sources ./
mv: cannot stat `./vm/PharoV20.sources': No such file or directory
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
11:21 p.m.
New subject: Build failed in Jenkins: moose-latest-dev-4.8 #220
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/220/>
------------------------------------------
Started by upstream project "fame" build number 24
originally caused by:
Started by user tudor(a)tudorgirba.com
Building remotely on moose-slave in workspace
<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/>
Deleting project workspace... done
[moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson9506030424781652.sh
+ bash
+ wget --quiet -O - http://get.pharo.org/20+vmLatest
Downloading the latest 20 Image:
http://files.pharo.org/image/20/latest.zip
image.ZCZju/Pharo-20596.image
Downloading the latest pharoVM:
http://files.pharo.org/vm/pharo/linux/pharo-linux-latest.zip
pharo-vm/pharo
Downloading PharoV10.sources:
http://files.pharo.org/image//PharoV10.sources.zip
Downloading PharoV20.sources:
http://files.pharo.org/image//PharoV20.sources.zip
Creating starter scripts pharo and pharo-ui
Please install the 32bit libraries
sudo aptitude install ia32-libs
+ ./vm.sh Pharo.image save moose-latest-dev-4.8
+ REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main
+ ./vm.sh moose-latest-dev-4.8.image config
http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose
--install=development
[31m[33m
===============================================================================
Notice: Installing ConfigurationOfMoose development
===============================================================================
[0m[0m+ ./vm.sh moose-latest-dev-4.8.image mooseimagesetup
+ ./vm.sh moose-latest-dev-4.8.image moosetest --junit-xml-output
[31m[33m
===============================================================================
Notice: Running tests in 126 Packages
===============================================================================
[0m[0m+ mv ./vm/PharoV20.sources ./
mv: cannot stat `./vm/PharoV20.sources': No such file or directory
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
8 Apr
8 Apr
1:19 a.m.
New subject: Build failed in Jenkins: moose-latest-dev-4.8 #221
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/221/>
------------------------------------------
Started by upstream project "glamour" build number 30
originally caused by:
Started by user tudor(a)tudorgirba.com
Started by upstream project "gtoolkit" build number 41
originally caused by:
Started by user tudor(a)tudorgirba.com
Started by user tudor(a)tudorgirba.com
Started by upstream project "petitjava" build number 15
originally caused by:
Started by user tudor(a)tudorgirba.com
Started by upstream project "petitparser" build number 32
originally caused by:
Started by user tudor(a)tudorgirba.com
Building remotely on moose-slave in workspace
<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/>
Deleting project workspace... done
[moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson5547030182177481900.sh
+ bash
+ wget --quiet -O - http://get.pharo.org/20+vmLatest
Downloading the latest 20 Image:
http://files.pharo.org/image/20/latest.zip
image.t8hJ7/Pharo-20596.image
Downloading the latest pharoVM:
http://files.pharo.org/vm/pharo/linux/pharo-linux-latest.zip
pharo-vm/pharo
Downloading PharoV10.sources:
http://files.pharo.org/image//PharoV10.sources.zip
Downloading PharoV20.sources:
http://files.pharo.org/image//PharoV20.sources.zip
Creating starter scripts pharo and pharo-ui
Please install the 32bit libraries
sudo aptitude install ia32-libs
+ ./pharo Pharo.image save moose-latest-dev-4.8
+ REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main
+ ./pharo moose-latest-dev-4.8.image config
http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose
--install=development
[31m[33m
===============================================================================
Notice: Installing ConfigurationOfMoose development
===============================================================================
[0m[0m+ ./pharo moose-latest-dev-4.8.image mooseimagesetup
+ ./pharo moose-latest-dev-4.8.image moosetest --junit-xml-output
[31m[33m
===============================================================================
Notice: Running tests in 126 Packages
===============================================================================
[0m[0m[31mMessageNotUnderstood: receiver of "hasPositiveExtent" is nil
[0mUndefinedObject(Object)>>doesNotUnderstand: #hasPositiveExtent
ScrollBar(Morph)>>invalidRect:from:
ScrollBar(Morph)>>invalidRect:
ScrollBar(Morph)>>position:
ScrollBar(Morph)>>bounds:
PaginatedMorphTreeMorph(ScrollPane)>>hResizeScrollBar
PaginatedMorphTreeMorph>>hResizeScrollBar
PaginatedMorphTreeMorph(ScrollPane)>>resizeScrollBars
PaginatedMorphTreeMorph(ScrollPane)>>extent:
PaginatedMorphTreeMorph(MorphTreeMorph)>>extent:
PaginatedMorphTreeMorph>>extent:
PaginatedMorphTreeMorph(Morph)>>bounds:
PaginatedMorphTreeMorph(Morph)>>layoutInBounds:
PaginatedMorphTreeMorph(Morph)>>layoutProportionallyIn:
ProportionalLayout>>layout:in: in Block: [:m | m layoutProportionallyIn: newBounds]
Array(SequenceableCollection)>>do:
PanelMorph(Morph)>>submorphsDo:
ProportionalLayout>>layout:in:
PanelMorph(Morph)>>doLayoutIn:
PanelMorph(Morph)>>fullBounds in Block: [self doLayoutIn: self layoutBounds]
BlockClosure>>on:do:
PanelMorph(Morph)>>fullBounds
PanelMorph(Morph)>>layoutProportionallyIn:
ProportionalLayout>>layout:in: in Block: [:m | m layoutProportionallyIn: newBounds]
Array(SequenceableCollection)>>do:
PanelMorph(Morph)>>submorphsDo:
ProportionalLayout>>layout:in:
PanelMorph(Morph)>>doLayoutIn:
PanelMorph(Morph)>>fullBounds in Block: [self doLayoutIn: self layoutBounds]
BlockClosure>>on:do:
[0mBuild step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
ERROR: Failed to archive test reports
hudson.util.IOException2: remote file operation failed:
<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/> at
hudson.remoting.Channel@4ce1e2b3:moose-slave
at hudson.FilePath.act(FilePath.java:848)
at hudson.FilePath.act(FilePath.java:825)
at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87)
at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:122)
at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:134)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810)
at
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:732)
at hudson.model.Run.execute(Run.java:1568)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
Caused by: hudson.util.IOException2: Failed to read
<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/Glamour-Tests-Morphic-Test.xml>
at hudson.tasks.junit.TestResult.parse(TestResult.java:244)
at hudson.tasks.junit.TestResult.parse(TestResult.java:163)
at hudson.tasks.junit.TestResult.parse(TestResult.java:140)
at hudson.tasks.junit.TestResult.<init>(TestResult.java:116)
at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:117)
at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:90)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2309)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Caused by: org.dom4j.DocumentException: Error on line 97 of document
file://<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/Glamour-Tests-Morphic-Test.xml>
: XML document structures must start and end within the same entity. Nested exception: XML
document structures must start and end within the same entity.
at org.dom4j.io.SAXReader.read(SAXReader.java:482)
at org.dom4j.io.SAXReader.read(SAXReader.java:264)
at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:129)
at hudson.tasks.junit.TestResult.parse(TestResult.java:227)
... 15 more
Caused by: org.xml.sax.SAXParseException; systemId:
file://<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/Glamour-Tests-Morphic-Test.xml;>
lineNumber: 97; columnNumber: 1; XML document structures must start and end within the
same entity.
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:391)
at
com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1404)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.endEntity(XMLDocumentFragmentScannerImpl.java:882)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.endEntity(XMLDocumentScannerImpl.java:582)
at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.endEntity(XMLEntityManager.java:1370)
at
com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1740)
at
com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipChar(XMLEntityScanner.java:1393)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2769)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:625)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:819)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:748)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525)
at org.dom4j.io.SAXReader.read(SAXReader.java:465)
... 18 more
4264
days inactive
4282
days old
27 comments
3 participants
participants (3)
-
admin＠moosetechnology.org -
Alexandre Bergel -
Tudor Girba