# Kernel Test Failed **Category:** [Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158) **Created:** 2005-04-08 20:50 UTC **Views:** 7 **Replies:** 5 **URL:** https://discourse.openehr.org/t/kernel-test-failed/15627 --- ## Post #1 by @Rodrigo_Filgueira1 I've downloaded maven, openehr kernel and JDK 1.5 update 2 for Windows XP. Installed JDK and Maven successfully, changed to base project directory and run 'maven test' First it started to download a lot of software log4j, commons, etc. Then tests started to be run and this is what I get in the end: **BUILD FAILED** **File...... C:\Documents and Settings\rodrigo\.maven\cache\maven-test-plugin-1.6.2\plugin.jelly** **Element... fail** **Line...... 181** **Column.... 54** **There were test failures.** **Total time: 10 seconds** **Finished at: Fri Apr 08 17:42:48 GMT-03:00 2005** I also have another question, one compiled, how should I use the kernel? cheers --- ## Post #2 by @Rodrigo_Filgueira1 Ok now. Tested this same procedure with a tweak in W2K and got: [junit] Testcase: testBuildAddress took 0.156 sec [junit] Testcase: testBuildPartyIdentity took 0.015 sec [junit] Testcase: testBuildContact took 0 sec [junit] Testcase: testBuildPartyRelationship took 0.032 sec [junit] Testcase: testBuildCapability took 0.015 sec [junit] Testcase: testBuildRole took 0.016 sec [junit] Testcase: testBuildActorSubclasses took 0.016 sec [junit] Running org.openehr.rm.util.RMObjectBuilderEHRTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.36 sec [junit] Testsuite: org.openehr.rm.util.RMObjectBuilderEHRTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.36 sec [junit] [junit] Testcase: testBuildEvaluation took 0.313 sec [junit] Testcase: testBuildObservation took 0.016 sec [junit] Testcase: testBuildInstruction took 0.015 sec [junit] Testcase: testBuildSection took 0 sec [junit] Testcase: testBuildComposition took 0.016 sec BUILD SUCCESSFUL Total time: 4 minutes 17 seconds Finished at: Wed Apr 13 16:41:34 GMT-03:00 2005 The only difference in this case was adding maven lib and lib/endorsed folders to the classpath. I really need to make this work on XP, any ideas? thank you all Rodrigo Filgueira wrote: --- ## Post #3 by @Rodrigo_Filgueira1 Rong, Thanks for your answer\. I still get the error messages in Windows XP, and the Install file states a successful compilation in XP\. My workstation at the university has XP and HP does not support W2K in this workstations, so I really need to make this work in XP\. Could anybody describe the environment configuration used when compiled in XP? thank you Rong Chen wrote: --- ## Post #4 by @Rodrigo_Filgueira1 More info on this problem\. I found the following failure report on test report "TEST\-org\.openehr\.rm\.datatypes\.quantity\.DvQuantityTest\.xml" <failure message="expected:<\.\.\.\.\.\.\.> but was:<\.\.\.,\.\.\.>" type="junit\.framework\.ComparisonFailure"> junit\.framework\.ComparisonFailure: expected:<\.\.\.\.\.\.\.> but was:<\.\.\.,\.\.\.>     at org\.openehr\.rm\.datatypes\.quantity\.DvQuantityTest\.testToString\(DvQuantityTest\.java:98\)     at sun\.reflect\.NativeMethodAccessorImpl\.invoke0\(Native Method\)     at sun\.reflect\.NativeMethodAccessorImpl\.invoke\(NativeMethodAccessorImpl\.java:39\)     at sun\.reflect\.DelegatingMethodAccessorImpl\.invoke\(DelegatingMethodAccessorImpl\.java:25\)     at org\.apache\.commons\.jelly\.tags\.ant\.AntTag\.doTag\(AntTag\.java:185\)     at org\.apache\.commons\.jelly\.impl\.TagScript\.run\(TagScript\.java:279\)     at org\.apache\.commons\.jelly\.impl\.ScriptBlock\.run\(ScriptBlock\.java:135\)     at org\.apache\.commons\.jelly\.TagSupport\.invokeBody\(TagSupport\.java:233\)     at org\.apache\.commons\.jelly\.tags\.core\.IfTag\.doTag\(IfTag\.java:88\)     at org\.apache\.commons\.jelly\.impl\.TagScript\.run\(TagScript\.java:279\)     at org\.apache\.commons\.jelly\.impl\.ScriptBlock\.run\(ScriptBlock\.java:135\)     at org\.apache\.maven\.jelly\.tags\.werkz\.MavenGoalTag\.runBodyTag\(MavenGoalTag\.java:79\)     at org\.apache\.maven\.jelly\.tags\.werkz\.MavenGoalTag$MavenGoalAction\.performAction\(MavenGoalTag\.java:110\)     at com\.werken\.werkz\.Goal\.fire\(Goal\.java:639\)     at com\.werken\.werkz\.Goal\.attain\(Goal\.java:575\)     at com\.werken\.werkz\.Goal\.attainPrecursors\(Goal\.java:488\)     at com\.werken\.werkz\.Goal\.attain\(Goal\.java:573\)     at org\.apache\.maven\.plugin\.PluginManager\.attainGoals\(PluginManager\.java:671\)     at org\.apache\.maven\.MavenSession\.attainGoals\(MavenSession\.java:263\)     at org\.apache\.maven\.cli\.App\.doMain\(App\.java:488\)     at org\.apache\.maven\.cli\.App\.main\(App\.java:1239\)     at sun\.reflect\.NativeMethodAccessorImpl\.invoke0\(Native Method\)     at sun\.reflect\.NativeMethodAccessorImpl\.invoke\(NativeMethodAccessorImpl\.java:39\)     at sun\.reflect\.DelegatingMethodAccessorImpl\.invoke\(DelegatingMethodAccessorImpl\.java:25\)     at com\.werken\.forehead\.Forehead\.run\(Forehead\.java:551\)     at com\.werken\.forehead\.Forehead\.main\(Forehead\.java:581\) </failure> I do not know exactly what it means since I'm no maven expert\. I checked out DvQuantityTest and did not find a problem\. Sounds more like a Maven problem\. Maybe because of the LOCALE settings? I'll give it a try\. Rong Chen wrote: --- ## Post #5 by @Rodrigo_Filgueira1 ok, that was it\. I changed regional settings to English\-United Kingdom and everything went fine\. Rodrigo Filgueira wrote: --- ## Post #6 by @rong.chen Rodrigo Filgueira wrote: > ok, that was it\. > I changed regional settings to English\-United Kingdom and everything went fine\. > > Rodrigo Filgueira wrote: > >> More info on this problem\. >> I found the following failure report on test report "TEST\-org\.openehr\.rm\.datatypes\.quantity\.DvQuantityTest\.xml" >> >> <failure message="expected:<\.\.\.\.\.\.\.> but was:<\.\.\.,\.\.\.>" type="junit\.framework\.ComparisonFailure"> >> junit\.framework\.ComparisonFailure: expected:<\.\.\.\.\.\.\.> but was:<\.\.\.,\.\.\.> >>    at org\.openehr\.rm\.datatypes\.quantity\.DvQuantityTest\.testToString\(DvQuantityTest\.java:98\) >> >>    at sun\.reflect\.NativeMethodAccessorImpl\.invoke0\(Native Method\) >>    at sun\.reflect\.NativeMethodAccessorImpl\.invoke\(NativeMethodAccessorImpl\.java:39\) >> >>    at sun\.reflect\.DelegatingMethodAccessorImpl\.invoke\(DelegatingMethodAccessorImpl\.java:25\) >> >>    at org\.apache\.commons\.jelly\.tags\.ant\.AntTag\.doTag\(AntTag\.java:185\) >>    at org\.apache\.commons\.jelly\.impl\.TagScript\.run\(TagScript\.java:279\) >>    at org\.apache\.commons\.jelly\.impl\.ScriptBlock\.run\(ScriptBlock\.java:135\) >>    at org\.apache\.commons\.jelly\.TagSupport\.invokeBody\(TagSupport\.java:233\) >>    at org\.apache\.commons\.jelly\.tags\.core\.IfTag\.doTag\(IfTag\.java:88\) >>    at org\.apache\.commons\.jelly\.impl\.TagScript\.run\(TagScript\.java:279\) >>    at org\.apache\.commons\.jelly\.impl\.ScriptBlock\.run\(ScriptBlock\.java:135\) >>    at org\.apache\.maven\.jelly\.tags\.werkz\.MavenGoalTag\.runBodyTag\(MavenGoalTag\.java:79\) >> >>    at org\.apache\.maven\.jelly\.tags\.werkz\.MavenGoalTag$MavenGoalAction\.performAction\(MavenGoalTag\.java:110\) >> >>    at com\.werken\.werkz\.Goal\.fire\(Goal\.java:639\) >>    at com\.werken\.werkz\.Goal\.attain\(Goal\.java:575\) >>    at com\.werken\.werkz\.Goal\.attainPrecursors\(Goal\.java:488\) >>    at com\.werken\.werkz\.Goal\.attain\(Goal\.java:573\) >>    at org\.apache\.maven\.plugin\.PluginManager\.attainGoals\(PluginManager\.java:671\) >>    at org\.apache\.maven\.MavenSession\.attainGoals\(MavenSession\.java:263\) >>    at org\.apache\.maven\.cli\.App\.doMain\(App\.java:488\) >>    at org\.apache\.maven\.cli\.App\.main\(App\.java:1239\) >>    at sun\.reflect\.NativeMethodAccessorImpl\.invoke0\(Native Method\) >>    at sun\.reflect\.NativeMethodAccessorImpl\.invoke\(NativeMethodAccessorImpl\.java:39\) >> >>    at sun\.reflect\.DelegatingMethodAccessorImpl\.invoke\(DelegatingMethodAccessorImpl\.java:25\) >> >>    at com\.werken\.forehead\.Forehead\.run\(Forehead\.java:551\) >>    at com\.werken\.forehead\.Forehead\.main\(Forehead\.java:581\) >> </failure> >> >> I do not know exactly what it means since I'm no maven expert\. I checked out DvQuantityTest and did not find a problem\. >> Sounds more like a Maven problem\. Maybe because of the LOCALE settings? >> >> I'll give it a try\. >> >> Rong Chen wrote: >> >>> Rodrigo Filgueira wrote: >>> >>> > I also have another question, one compiled, how should I use the kernel? >>> > >>> > cheers >>> >>> Hi Rodrigo, >>> >>> Sorry for the delay\. For some reason your emails didn't reach my email client, I only saw them on the openEHR web until today\. It's good that you can compile the kernel at last\. >>> >>> For your question, the openEHR kernel is a core component for other components to be built around it to form a larger piece of software \- e\.g\. an EHR system\. We are in the process of releasing a java ADL parser under open source license, which is based on the kernel\. There will hopefully be more components available both from us and other openEHR implementers\. >>> >>> Regards, >>> Rong >>> >>> ACODE >>> www\.acode\.se >>> >> >> \- >> If you have any questions about using this list, >> please send a message to d\.lloyd@openehr\.org > > \- > If you have any questions about using this list, > please send a message to d\.lloyd@openehr\.org > Thanks for reporting this to us\! It turns out to be a bug in the unit test code \(DvQuantityTest\)\. It uses a hard coded string to verify toString\(\) of DvQuantity, and that string includes a decimal separator, which is decided by the default locale\. For different locale, the separator could be different\. I have fixed it in the repository now\. Regards, Rong --- **Canonical:** https://discourse.openehr.org/t/kernel-test-failed/15627 **Original content:** https://discourse.openehr.org/t/kernel-test-failed/15627