Hi,
I'll have a look once the current build finishes. The problem might be just
a manifestation of something going wrong elsewhere. I have the same problem
related to keyNotFound in another build but the xml produced is correct.
I'm refering to this stack and I'll have a look at the test failing:
[31mKeyNotFound: key 'Integer' not found in Dictionary
[0mDictionary>>errorKeyNotFound:
Dictionary>>at: in Block: [ self errorKeyNotFound: key ]
Dictionary>>at:ifAbsent:
Dictionary>>at:
MoosePragmaProcessor(FMPragmaProcessor)>>ensureClass: in Block: [
metaDict at: var asString ]
Dictionary>>at:ifAbsent:
MoosePragmaProcessor(FMPragmaProcessor)>>ensureClass:
MoosePragmaProcessor(FMPragmaProcessor)>>resolveObjectReferences in
Block: [ :prop :value | prop type: (self ensureClass: val...etc...
IdentityDictionary(Dictionary)>>keysAndValuesDo: in Block: [ :assoc |
aBlock value: assoc key value: assoc va...etc...
IdentityDictionary(Dictionary)>>associationsDo: in Block: [ :each |
each ifNotNil: [ aBlock value: each ] ]
Array(SequenceableCollection)>>do:
IdentityDictionary(Dictionary)>>associationsDo:
IdentityDictionary(Dictionary)>>keysAndValuesDo:
MoosePragmaProcessor(FMPragmaProcessor)>>resolveObjectReferences
MoosePragmaProcessor(FMPragmaProcessor)>>run
MooseModel class>>metaBuilder:withProcessor:
MooseModel class>>metaBuilder:
MooseModel class>>metaTower
MooseModel class>>meta
MooseModel class>>importFrom:
MooseModel>>importFromMSEStream:
MooseSampleData>>readMSEString:
MooseSampleData>>initialize
MooseSampleData class(Behavior)>>new
MooseSampleData class(TestResource class)>>new
MooseSampleData class(TestResource class)>>makeAvailable
MooseSampleData class(TestResource class)>>isAvailable
HDTestReport>>setUp in Block: [ :each | ...
OrderedCollection>>do:
HDTestReport>>setUp
On Mon, Mar 17, 2014 at 6:24 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
Hi,
I tried to look in the the failing build problem, but I could not solve
it.
Somehow the Moose-Tests-Core.xml is incomplete on the build server.
I tried to reproduce the problem locally, but I did not manage with this
code:
MooseTestCommandLineHandler activateWith: (CommandLineArguments
withArguments: {'--junit-xml-output'})
This should be the correspondent of:
./pharo $JOB_NAME.image moosetest --junit-xml-output
Could anyone else try as well?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev