It should be some environmental issue.
I can successfully run the smoke test on Windows 8,
 
And the JVM is:
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
 
Regards

On Mon, Oct 13, 2014 at 8:35 PM, Peter Cai <qutpeter@gmail.com> wrote:
OS: Linux dev-01 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux  (Ubuntu 14.04 desktop)

JVM:
 java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)

My guess is environmental issue as well. But can't find anything so far.

Regards,
Peter



On Mon, Oct 13, 2014 at 8:29 PM, Tomaž Cerar <tomaz.cerar@gmail.com> wrote:
os? jvm? arch?

looking at our nightly jobs whole testsuite passes on our CI with JDK7 & 8 on windows and on linux.

I am guessing it must be environmental issue.

On Mon, Oct 13, 2014 at 11:47 AM, Peter Cai <qutpeter@gmail.com> wrote:
Hi,

It looks like that the current HEAD of Wildfly will failed when running smoke testing with the following information:

Results :

Failed tests:
  ServerInModuleDeploymentTestCase.testDeploymentStreamApi:93->testDeployments:614 expected:<[c767c5d5e516f6e04ec69f5a0f8ccdc0d63e6fa5, 342ae7aec9bff370e3de8704ed9642a718986e61]> but was:<[342ae7aec9bff370e3de8704ed9642a718986e61]>

Any cues?

Regards,

_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev