Build failed in Jenkins: moose-latest-dev-4.8 #799
by admin＠moosetechnology.org
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/799/>
------------------------------------------
[...truncated 140 lines...]
new:
replaceFrom:to:with:startingAt:
at:put:
at:put:
at:put:
instVarAt:
basicNew
new:
new:
replaceFrom:to:with:startingAt:
at:put:
at:put:
new:
replaceFrom:to:with:startingAt:
at:put:
at:put:
at:put:
at:put:
at:put:
instVarAt:
at:put:
at:put:
instVarAt:
at:put:
at:put:
instVarAt:
at:put:
at:put:
class
at:put:
class
class
fuelPointsTo:
class
at:put:
class
at:put:
at:put:
class
at:put:
class
class
fuelPointsTo:
new:
replaceFrom:to:with:startingAt:
at:put:
at:put:
at:put:
basicNew
new:
new:
replaceFrom:to:with:startingAt:
at:put:
at:put:
new:
replaceFrom:to:with:startingAt:
at:put:
at:put:
at:put:
at:put:
at:put:
at:put:
at:put:
class
class
fuelPointsTo:
new:
replaceFrom:to:with:startingAt:
at:put:
at:put:
at:put:
instVarAt:
basicNew
new:
new:
replaceFrom:to:with:startingAt:
at:put:
at:put:
new:
replaceFrom:to:with:startingAt:
at:put:
at:put:
at:put:
at:put:
at:put:
instVarAt:
at:put:
at:put:
instVarAt:
at:put:
at:put:
instVarAt:
at:put:
at:put:
class
at:put:
class
class
fuelPointsTo:
class
at:put:
class
at:put:
at:put:
class
at:put:
class
class
fuelPointsTo:
new:
replaceFrom:to:with:startingAt:
at:put:
at:put:
at:put:
basicNew
new:
new:
replaceFrom:to:with:startingAt:
at:put:
at:put:
new:
replaceFrom:to:with:startingAt:
at:put:
at:put:
at:put:
at:put:
at:put:
at:put:
at:put:
class
class
new:
at:put:
at:put:
at:put:
instVarAt:
basicNew
new:
new:
at:put:
at:put:
new:
at:put:
at:put:
at:put:
at:put:
at:put:
instVarAt:
at:put:
at:put:
instVarAt:
at:put:
at:put:
instVarAt:
at:put:
at:put:
class
at:put:
class
class
fuelPointsTo:
class
at:put:
class
at:put:
at:put:
class
class
new:
replaceFrom:to:with:startingAt:
at:put:
millisecondClockValue
signal
at:put:
at:put:
at:put:
at:put:
at:put:
primSignal:atMilliseconds:
millisecondClockValue
wait
stack page bytes 4096 available headroom 3300 minimum unused headroom 3484
(last object overwritten)
./pharo: line 11: 29064 Aborted (core dumped) "$DIR"/"pharo-vm/pharo" -nodisplay "$@"
Build 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@2f17e8fb:moose-ubuntu1204-dualproc-i386
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/Moose-Tests-Smallta...>
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 123 of document file://<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/Moose-Tests-Smallta...> : 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/Moose-Tests-Smallta...;> lineNumber: 123; 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
9 years, 7 months
better rubric-glamour integration
by Tudor Girba
Hi,
Alain took some time and provided an enhanced integration of Rubric into
Glamour. This means that now you can use all the power of Rubric from
Glamour.
For example, select a class from a system parsed with VerveineJ, then open
it in a Glamour Editor, and then use this code:
composer rubricText with: [ :r |
r display: [ :c | class sourceAnchor completeText ].
class methods do: [ :m | | seg |
m sourceAnchor notNil ifTrue: [
seg := RubTextSegmentMorph
from: m sourceAnchor interval first
to: m sourceAnchor interval last + 1.
seg color: Color paleYellow.
seg icon: MooseIcons famixMethod.
seg label: 'Explore'.
seg iconBlock: [ :segment :event | m explore ].
r addTextSegment: seg ] ] ].
composer startOn: class
You get all methods in the class highlighted and you can interact with them
(see the attached screenshot).
This is highly promising. For more examples, look at GLMRubricExample and
its subclasses.
The next step will be to replace altogether the default text presentation
with the new Rubric rendering.
Cheers,
Doru
[image: Inline image 1]
--
www.tudorgirba.com
"Every thing has its own flow"
9 years, 7 months
FamixDiff
by Nicolas Anquetil
announcing version 0.9 of FamixDiff:
MCHttpRepository
location: 'http://www.smalltalkhub.com/mc/Moose/FamixDiff/main'
user: ''
password: ''
With Anne, we have been working on a diffing algorithm between Famix models.
The idea is that having models of two versions of the same system, you
can generate the list of changes (add/delete/move/rename) that bring the
first model to the second.
Still work in progress, but we are dealing with the main entities:
package/namespaces, classes, methods, variables
Nicolas (& Anne)
--
Nicolas Anquetil -- RMod research team (Inria)
9 years, 8 months
