Eclipse Community Forums: Remote Application Platform (RAP) » Test failures on current HEAD and RC4

Home » Eclipse Projects » Remote Application Platform (RAP) » Test failures on current HEAD and RC4(I tried to run a simple mvn clean verify and got lots of test failures/errors)

Show: Today's Messages :: Show Polls :: Message Navigator

Test failures on current HEAD and RC4 [message #1698863]

Thu, 18 June 2015 13:01

Nicolai Czempin

Messages: 13
Registered: June 2015

Junior Member

During the course of examining other issues I cloned the rap project and tried a simple "mvn clean verify", as suggested in the Readme.MD.

However, first on commit cc1917688a07e44a1c48ea48090ff4428a0dde28 (from June 12) and then on the tag 3.0.0-RC4 (0494e78bff8f7328dc31c22fd8084cb639497b08), when I ran this everything seemed to be built just fine, but there were various test failures.

Before I try and go into details and send you the full log or something, is there anything that I need to be careful about regarding my configuration? Your Jenkins builds of the same commits seem to have no problems.

Here are some details on my system:

...>java -version
java version "1.8.0_05"
Java(TM) SE Runtime Environment (build 1.8.0_05-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.5-b02, mixed mode)

...>mvn -version
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T18:29:23+01:00)
Maven home: C:\apache-maven-3.2.5\bin\..
Java version: 1.8.0_05, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_05\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"

The only two other things that I can think of as potentially having an effect:
1) My %TEMP% is on a RAM disk (I got several errors saying that things couldn't be deleted).
2) All 12 threads of my 6-core machine were quite busy with unrelated work at the time I ran the build. Other resources such as HDD/SDD space, RAM, were likely to be sufficient (but I don't know how much I need, in any case there were no error messages directly pointing to lack of resources).

I will provide more details if necessary, in general tests started failing near the ...rwt.cluster... tests, and then not entirely consistently reproducibly varoius tests failed (I switched to RC4 at some point, the failures were different. I did not try to look for reproducibility and wanted to ask here first if there are any prerequisites that I may have missed.)

Report message to a moderator

Re: Test failures on current HEAD and RC4 [message #1698943 is a reply to message #1698863]

Fri, 19 June 2015 05:11

Ivan Furnadjiev

Messages: 2426
Registered: July 2009
Location: Sofia, Bulgaria

Senior Member

Hi,
this is the known problem with Java 8. Please execute the test s with
Java 7.
HTH,
Ivan

--
Ivan Furnadjiev

Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/

Report message to a moderator

Re: Test failures on current HEAD and RC4 [message #1698991 is a reply to message #1698943]

Fri, 19 June 2015 11:13

Nicolai Czempin

Messages: 13
Registered: June 2015

Junior Member

I ran the test with Java 7, and I also put my %TEMP% and %TMP% paths on a real hard drive, to get rid of the spurious "could not delete" errors.

Now I'm getting a consistent test failure in org.eclipse.rap.rwt.internal.resources.ClientResources_Test.testIncludesDebugSettings:

-------------------------------------------------------------------------------
Test set: org.eclipse.rap.rwt.internal.resources.ClientResources_Test
-------------------------------------------------------------------------------
Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.932 sec <<< FAILURE! - in org.eclipse.rap.rwt.internal.resources.ClientResources_Test
testIncludesDebugSettings(org.eclipse.rap.rwt.internal.resources.ClientResources_Test)  Time elapsed: 0.176 sec  <<< FAILURE!
java.lang.AssertionError: null
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.junit.Assert.assertTrue(Assert.java:52)
	at org.eclipse.rap.rwt.internal.resources.ClientResources_Test.testIncludesDebugSettings(ClientResources_Test.java:81)

This is on the RC4 tag, Java version: 1.7.0_51. (64)

Report message to a moderator

Re: Test failures on current HEAD and RC4 [message #1715652 is a reply to message #1698991]

Wed, 25 November 2015 03:11

Chris Fairhall

Messages: 221
Registered: February 2011

Senior Member

I'd say this is a line termination issue.
I encountered this today and upon debugging, found the test is looking for a string with \n terminators, but the file has \r\n thanks to the default Windows Git setting of converting local files to Windows terminators and remote files to Unix

Report message to a moderator

Previous Topic:	Image scaling with max-height and max-width CSS properties on the client side
Next Topic:	Markup issues with accent

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 09:00:09 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter