dukeboard / kevoree-modeling-framework

Kevoree Modeling Framework

Home Page:http://kevoree.org/kmf

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Test failure

StephaneMangin opened this issue · comments

The output :


T E S T S

Running org.kevoree.modeling.microframework.typescript.NoJs_MainTest
Extract /home/blacknight/.nodejs/v0.10.20/node-v0.10.20-linux-x64.tar.gz START
Extract /home/blacknight/.nodejs/v0.10.20/node-v0.10.20-linux-x64.tar.gz DONE
déc. 27, 2014 1:25:14 PM NodejsExecutable start
INFOS: de.flapdoodle.embed.nodejs.NodejsConfig@66d33a
[nodejs error]
[nodejs error] undefined:4
[nodejs error] __.prototype = b.prototype;
[nodejs error] ^
[nodejs error] TypeError: Cannot read property 'prototype' of undefined
[nodejs error] at __extends (eval at (/home/blacknight/projects/kevoree-modeling-framework/org.kevoree.modeling.microframework.typescript/target/test-classes/MyTestRunner.js:6:98), :4:21)
[nodejs error] at eval (eval at (/home/blacknight/projects/kevoree-modeling-framework/org.kevoree.modeling.microframework.typescript/target/test-classes/MyTestRunner.js:6:98), :7147:25)
[nodejs error] at api.abs.api.abs (eval at (/home/blacknight/projects/kevoree-modeling-framework/org.kevoree.modeling.microframework.typescript/target/test-classes/MyTestRunner.js:6:98), :7156:23)
[nodejs error] at modeling.api.modeling.api (eval at (/home/blacknight/projects/kevoree-modeling-framework/org.kevoree.modeling.microframework.typescript/target/test-classes/MyTestRunner.js:6:98), :8106:19)
[nodejs error]
at kevoree.modeling.kevoree.modeling (eval at (/home/blacknight/projects/kevoree-modeling-framework/org.kevoree.modeling.microframework.typescript/target/test-classes/MyTestRunner.js:6:98), :8107:15)
[nodejs error] at org.kevoree.org.kevoree (eval at (/home/blacknight/projects/kevoree-modeling-framework/org.kevoree.modeling.microframework.typescript/target/test-classes/MyTestRunner.js:6:98), :8108:11)
[nodejs error] at org (eval at (/home/blacknight/projects/kevoree-modeling-framework/org.kevoree.modeling.microframework.typescript/target/test-classes/MyTestRunner.js:6:98), :8109:7)
[nodejs error] at Object.eval (eval at (/home/blacknight/projects/kevoree-modeling-framework/org.kevoree.modeling.microframework.typescript/target/test-classes/MyTestRunner.js:6:98), :8110:3)
[nodejs error] at Object. (/home/blacknight/projects/kevoree-modeling-framework/org.kevoree.modeling.microframework.typescript/target/test-classes/MyTestRunner.js:6:1)
[nodejs error] at Module._compile (module.js:456:26)
[nodejs error]
déc. 27, 2014 1:25:14 PM de.flapdoodle.embed.process.io.file.Files forceDelete
INFOS: Could delete /tmp/extract-020cf098-5c81-4a7c-9bea-98dfa06f6e9fnode.pid
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.544 sec <<< FAILURE!
déc. 27, 2014 1:25:14 PM de.flapdoodle.embed.process.io.file.Files forceDelete
INFOS: Could delete /tmp/extract-020cf098-5c81-4a7c-9bea-98dfa06f6e9fnode
déc. 27, 2014 1:25:14 PM de.flapdoodle.embed.process.store.CachingArtifactStore removeFileSet
AVERTISSEMENT: Allready removed de.flapdoodle.embed.process.extract.ImmutableExtractedFileSet@1888ff2c for V0_10:Linux:B64, emergency shutdown?

Results :

Failed tests: baseTest(org.kevoree.modeling.microframework.typescript.NoJs_MainTest): expected:<0> but was:<8>

Tests run: 1, Failures: 1, Errors: 0, Skipped: 0

Hello,

Really thanks because i'm looking for this error since a while ! :-)
I can't reproduce on any of our environment but if you sent me this zipped target directory of the project : org.kevoree.modeling.microframework.typescript i can fix it.

Hello,

Here comes the zip of the folder you requested... http://www.tempfiles.net/download/201412/364055/org.html

You can delete this file after downloading it : http://www.tempfiles.net/delfile/201412/364055/6108c684/org.html

Thanx for your reactivity :)

Perfect, i will look at asap. Seems to be a simple issue. Anyway you can still use the last compiled version on the maven repository because the issue is only appearing when you compile KMF itself

Hello,
This issue should be fixed right now in the snapshot version. At least on our build environment similar to yours it is fixed. Can you confirme it before I do the release ?